On Fri, 2005-04-29 at 10:44 -0700, Robin H. Johnson wrote: > On Fri, Apr 29, 2005 at 09:36:54AM +0900, Jason Stubbs wrote: > > What about the unused `ebuild [ebuild] config`? Isn't that the perfect > > place > > for this sort of stuff? The only package that I know that uses this feature > > is mysql. There are way more possibilities. > No, ebuild config shouldn't be abused like this. Say I have an existing > install of mysql, and the package maintainer puts in an updated > logrotate.d file. Running 'ebuild mysql.ebuild config' is meant for NEW > installations only, and it doesn't enable me to take advantage of > CONFIG_PROTECT. I've seen a package where running the config phase when > the package is already set up blows away your existing config. It gives > you a warning first, but how would I then get an updated logrotate.d > file?
Ehh, actually this got kinda hijacked and we were kinda discussing something else, as spyderous was talking about providing a package with configuration files and other such files. We diverged a bit saying how config should be used more, but I know that at least *I* wasn't talking about for things like logrotate files, but rather for actually configuring a package. > I see only two viable options. > - Unconditional, use INSTALL_MASK, no RDEPEND on logrotate > - Conditional on USE=logrotate > > The first one is what is generally used in the tree so far. -- Chris Gianelloni Release Engineering - Strategic Lead/QA Manager Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
