From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Segregating KDE?
Date: Sun, 19 Sep 2004 21:46:11 +0200 [thread overview]
Message-ID: <200409192146.18527.pauldv@gentoo.org> (raw)
In-Reply-To: <200409191756.18289.danarmak@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
On Sunday 19 September 2004 16:56, Dan Armak wrote:
> On Sunday 19 September 2004 07:43, Duncan wrote:
> > Then, at the top of the file put a big hairy warning about how some
> > package components, particularly in kdebase, are depended on by others,
> > and to disable the use flag and recompile all packages if there are
> > dependency issues, and then leave everything else up to the user. Any
> > bugs on related dependency issues would be marked invalid, see the
> > warning in the file, etc. so it wouldn't become a big support issue.
>
> As you say, this solution is hairy (or anything else that doesn't create
> real separate ebuilds for the separate apps). I personally don't like it at
> all and don't really want to see it happen even as an alternative to
> nothing at all, because it's so ugly. Of course, it's very easy to
> implement, but it takes away all the advantages of having a proper package
> manager - all the advantages of using portage rather than state-less
> invocations on the order of 'ebuild.sh file.ebuild'...
>
> And of course this solution entails more or less not supporting it despite
> having it in the portage tree - marking related bugs as invalid etc. That's
> another reason I don't like it.
>
> Perhaps I don't have the right to say this at this point, having been
> incative for over a year, but this solution simply takes away too much
> functionality and support from the user in order to decrease the
> maintainer's workload.
Well, I'll second you in any case. It is not a solution and offering something
willingly and then saying it is unsupported is in these kinds of cases a
medicine worse than the cure. The only "possible" solution I see would
involve useflags and useflag dependencies (still "in the works"). But I agree
that we must avoid in any case to get back the stateless mess that the lack
of dependency tracking entails.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-19 19:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 7:57 [gentoo-dev] Segregating KDE? Anthony Gorecki
2004-09-18 9:16 ` Dan Armak
2004-09-18 18:02 ` Anthony Gorecki
2004-09-18 18:29 ` Dan Armak
2004-09-18 18:31 ` Dan Armak
2004-09-18 19:19 ` Seemant Kulleen
2004-09-18 19:36 ` Dan Armak
2004-09-19 8:30 ` Simone Gotti
2004-09-19 14:48 ` Dan Armak
2004-09-19 18:08 ` Simone Gotti
2004-09-19 19:33 ` Dan Armak
2004-09-19 19:42 ` Dan Armak
2004-09-19 19:59 ` Dan Armak
2004-09-19 21:00 ` Simone Gotti
2004-09-21 0:10 ` Simone Gotti
2004-09-18 19:09 ` Anthony Gorecki
2004-09-18 19:45 ` Dan Armak
2004-09-18 20:13 ` Anthony Gorecki
2004-09-18 20:33 ` Sami Samhuri
2004-09-18 20:33 ` Anthony Gorecki
2004-09-18 20:38 ` Dan Armak
2004-09-18 20:40 ` Dan Armak
2004-09-19 4:43 ` [gentoo-dev] " Duncan
2004-09-19 14:56 ` Dan Armak
2004-09-19 19:46 ` Paul de Vrieze [this message]
2004-09-18 13:11 ` [gentoo-dev] " Caleb Tennis
2004-09-18 14:06 ` Nick Dimiduk
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=200409192146.18527.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--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