On Fri, 2006-06-09 at 16:35 -0400, Chris Gianelloni wrote: > This is the "official" (hehe) request for comments on making a policy of > how to handle ebuilds than can be used for either client or server and > how to allow for building client-only. > > The idea is quite simple. > > Gentoo's standard operating procedure is to build packages as they were > intended and packaged from upstream. This means if the client and the > server for a particular package is in a single package, we should build > both by default. To facilitate building the client portions only, the > use of the local "minimal" USE flag is allowed. This can be shown in > the openldap and dhcp ebuilds.
That is backwards however. The first ebuild to take advantage of building server/client was net-snmp and it uses minimal to build only the snmpd, snmptrapd. Sense then others have been bastardizing the USE flag. Being that net-snmp was historically first in doing this I'd rather not have to change all my setups on all my servers to accommodate your idea of inverting the logic of declaring it minimal to mean client-only. > Each package which uses this flag should > document what is built when the "minimal" USE flag is in use, via > use.local.desc as it will remove any ambiguity into what is being done. > Because of this, I would request that "minimal" not become a global USE > flag, since its meaning would actually be different between some > packages, Seems logical. But for what you are proposing I'd suggest not making USE of minimal at all for this. I'd rather see that flag reserved for mostly embedded alike use. -peace -- Ned Ludd <[EMAIL PROTECTED]> Gentoo Linux -- gentoo-dev@gentoo.org mailing list
