From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Sun, 16 May 2010 12:49:14 -0600 From: EBo To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: <378a974db06785ba68237c70411d9e41@kw.quanstro.net> References: <6aaf2d79af665bf1905db13e44e194e5@quanstro.net> <3c68655ad1dadf393d44b4a945abbd7a@swcp.com> <26f3b3b7fc6f7e8e8d90094305925bdd@kw.quanstro.net> <378a974db06785ba68237c70411d9e41@kw.quanstro.net> Message-ID: <05efeb46a13b81ef20914458e84cdd9f@swcp.com> User-Agent: RoundCube Webmail/0.3.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] nupas update Topicbox-Message-UUID: 24fb4b6a-ead6-11e9-9d60-3106f5b1d025 >> I think some of the ideas behind portage are good, e.g. the ability to >> handle patches and slim down software via USE flags. > > this is only necessary if your purpose is to prune overgrown > packages. i hope will will solve this problem by not having > overgrown pacakges. I see a couple of other applications for use flags besides pruning overgrown packages -- such as should we install source and documentation (yes by default on large systems, no on small embedded systems). Should we strip binaries or compile things for debugging? Install examples? I do not see much call for more than that, but I see those as useful. Another potential use flag or architecture keyword covers if the package can be built, or should build, using 64 bit mode. EBo --