From: Mike Myers <fluffymikey@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] KDE, metapackages, and monolithic packages
Date: Sat, 25 Feb 2006 02:32:21 -0600 [thread overview]
Message-ID: <44001615.4030707@gmail.com> (raw)
Hello!
Currently, as you all surely already know, KDE is currently handled with
metapackages or monolithic packages. The metapackages is very
convenient for a more complete install of KDE, and the monolithic
packages are better or a more modular install. However, with the
metapackages, it seems much more difficult than necessary to rebuild the
KDE packages. Like, say I wanted to add a user flag to support
something I just added, like xinerama support. With metapackages the
way they are now, I would have to completely uninstall every single
package and then reemerge the metapackage and it's dependencies. Just
simply reemerging the metapackage doesn't actually recompile anything.
Also, if I wanted to add support for part of KDE, like say, alsa support
for kdemultimedia, I would have to manually unemerge each individual
package related to kdemultimedia and then reemerge the metapackage.
My question is; Is there any better way to do these kinds of things
yet? If not, are there any plans for making this kind of process any
easier for the users? I really like KDE and I'm sure there are a lot of
other people that do as well. I can understand the reason for going to
metapackages, but it doesn't seem to have been as smooth of a process as
intended. At least not in some aspects. I am not a developer, and I
apologize if this has already been addressed. I haven't seen anything
related to this issue. The KDE howto docs seem to assume the user is
doing an initial install and it doesn't address if part of a metapackage
is to be reinstalled. It also suggests metapackages over monolithic
packages. I'm not really sure of the reason for such a suggestion if
making a change to the USE flags is going to be so difficult.
Maybe somebody can clear this up for me? Again, I apologize if this has
already been addressed.
Thanks,
Mike
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2006-02-25 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 8:32 Mike Myers [this message]
2006-02-25 9:06 ` [gentoo-dev] KDE, metapackages, and monolithic packages Diego 'Flameeyes' Pettenò
2006-02-25 18:33 ` Mike Myers
2006-02-25 18:44 ` Sebastian Bergmann
2006-02-25 18:45 ` John Myers
2006-02-25 20:07 ` Mike Myers
2006-02-25 20:15 ` Matthijs van der Vleuten
2006-02-26 10:52 ` [gentoo-dev] " Duncan
2006-02-26 23:05 ` Mike Myers
2006-02-27 0:56 ` Richard Fish
2006-02-27 10:09 ` Paul de Vrieze
2006-02-28 0:13 ` [gentoo-dev] " Duncan
2006-02-25 9:06 ` [gentoo-dev] " Petteri Räty
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=44001615.4030707@gmail.com \
--to=fluffymikey@gmail.com \
--cc=gentoo-dev@lists.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