From: EBo <ebo@sandien.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nupas update
Date: Sun, 16 May 2010 12:49:14 -0600 [thread overview]
Message-ID: <05efeb46a13b81ef20914458e84cdd9f@swcp.com> (raw)
In-Reply-To: <378a974db06785ba68237c70411d9e41@kw.quanstro.net>
>> 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 --
next prev parent reply other threads:[~2010-05-16 18:49 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 2:16 erik quanstrom
2009-09-03 2:29 ` David Leimbach
2009-09-03 2:37 ` erik quanstrom
2010-05-15 23:17 ` Akshat Kumar
2010-05-15 23:45 ` erik quanstrom
2010-05-16 2:36 ` ron minnich
2010-05-16 4:15 ` erik quanstrom
2010-05-16 4:28 ` Akshat Kumar
2010-05-16 4:35 ` ron minnich
2010-05-16 4:39 ` erik quanstrom
2010-05-16 4:51 ` ron minnich
2010-05-16 4:57 ` Akshat Kumar
2010-05-16 5:44 ` ron minnich
2010-05-16 13:42 ` EBo
2010-05-16 14:03 ` erik quanstrom
2010-05-16 14:51 ` Ethan Grammatikidis
2010-05-16 15:37 ` EBo
2010-05-16 15:53 ` Ethan Grammatikidis
2010-05-16 16:02 ` ron minnich
2010-05-16 17:10 ` Ethan Grammatikidis
2010-05-16 17:19 ` EBo
2010-05-16 15:21 ` EBo
2010-05-16 15:42 ` Ethan Grammatikidis
2010-05-16 17:34 ` EBo
2010-05-16 17:47 ` hiro
2010-05-16 18:58 ` Corey
2010-05-16 19:29 ` EBo
2010-05-18 21:35 ` Georg Lehner
2010-05-18 22:07 ` ron minnich
2010-05-16 15:46 ` Jorden M
2010-05-16 15:59 ` Ethan Grammatikidis
2010-05-16 15:42 ` Jorden M
2010-05-16 18:24 ` erik quanstrom
2010-05-16 18:49 ` EBo [this message]
2010-05-16 20:44 ` erik quanstrom
2010-05-16 21:44 ` EBo
2010-05-17 1:17 ` erik quanstrom
2010-05-17 1:52 ` EBo
2010-05-17 1:58 ` erik quanstrom
2010-05-17 1:35 ` Akshat Kumar
2010-05-17 4:09 ` ron minnich
2010-05-17 4:19 ` erik quanstrom
2010-05-17 4:56 ` ron minnich
2010-05-18 23:50 ` Federico G. Benavento
2010-05-18 23:59 ` ron minnich
2010-05-19 0:40 ` Jorden M
2010-05-19 1:40 ` Robert Ransom
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 15:23 erik quanstrom
2008-10-23 0:08 erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05efeb46a13b81ef20914458e84cdd9f@swcp.com \
--to=ebo@sandien.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).