From: Dave Lee <davel@canuck.com>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Sys-Cleanup after build complete
Date: Tue, 19 Feb 2002 07:25:02 -0700 [thread overview]
Message-ID: <Pine.SGI.4.21.0202190704210.7977474-100000@the-gimp> (raw)
In-Reply-To: <1014004250.5927.6.camel@uranus.u235.eyep.net>
Vitaly Kushneriuk wrote:
> Your problem can be solved with sub-packaging. i.e. producing
> more then one package from the same ebuild. like glibc and glibc-devel.
> This feature is considered for the next generation of portage (after 1.0
> is out).
Is there anybody else out there other than me who doesnt like this?
my experience is with rpm based systems and I hate the proliferation of
-devel packages and other subpackages. thats one thing I really like about
portage is that I dont have to deal with that, I install a package and it
comes with everything. I know there are advantages to having -devel and
other subpackages like the rpm systems use, such as finer grained control
of what is and isnt installed, but as a user and administrator I hate
having extra packages installed as though they are different from the
package itself. most software compiled from source will install the devel
files, and I think portage should too. maybe a solution is to have a
USE_DEVEL that is used similar to USE, and can be default set to "*" for
everything. another possibility is to have a --option to emerge so that
emereg doesnt install devel files. I am new to gentoo so forgive me if
these ideas suck and I will just shutup in that case.
thanks,
Dave
next prev parent reply other threads:[~2002-02-19 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000601c1b923$f0d57740$be01a8c0@KISSWebMedias>
2002-02-18 3:50 ` [gentoo-dev] Sys-Cleanup after build complete Vitaly Kushneriuk
2002-02-19 9:20 ` AW: " Sebastian Werner
2002-02-18 4:05 ` Vitaly Kushneriuk
2002-02-19 14:25 ` Dave Lee [this message]
2002-02-19 14:00 ` Bob Phan
2002-02-19 18:42 ` George Shapovalov
2002-02-19 15:00 ` Vitaly Kushneriuk
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=Pine.SGI.4.21.0202190704210.7977474-100000@the-gimp \
--to=davel@canuck.com \
--cc=gentoo-dev@gentoo.org \
/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