I've added "Cc: tech-pkg".

In message <45330BB6.3030805@bl.echidna.id.au>
	on Mon, 16 Oct 2006 14:33:58 +1000,
	Carl Brewer <carl@bl.echidna.id.au> wrote:
> Takahiro Kambe wrote:
> > In message <4511FA37.2090700@bl.echidna.id.au>
> > 	on Thu, 21 Sep 2006 12:34:31 +1000,
> > 	Carl Brewer <carl@bl.echidna.id.au> wrote:
> >>> Anyway, zope packages' installation directory should be based on
> >>> common policy.  I think that it is better to change zope29's ZOPEDIR
> >>> to ${PREFIX}/share/zope (or ${PREFIX}/zope?).
> >> With the way zope (and Plone etc) work, is it necessarily such a good
> >> idea to even have them in pkgsrc?  I'm not 100% sure.  I'm running zope
> >> (2.9.4 atm) and Plone outside of pkgsrc, and having their volatile data 
> >> (the server/ directory where all the funky stuff goes) in /usr/pkg seems
> >> to me to be suboptimal?
> > "out of pkgsrc" is one idea.  But if you really happy with installing
> > plone or zope with single pkg_add command execition?  Especially if
> > you need to setup (or update) them on many machines?
> > 
> >> I'm sure with sufficient hacking, they can be made to
> >> keep their datafiles etc somewhere reasonable?
> > What do you call "datafiles"?  Zope instance??
> 
> data.fs, all the logs etc, so yes, instances of zope.  IMO, they
> don't really belong in /var.
Why?  AFAIK, they are none-shareable data files and Zope instances
might be multple exists on the same machine.

(And they would be under ${VARBASE} which default to /var, but you can
change it.)

-- 
Takahiro Kambe <taca@back-street.net>