From: Stephan Hermann <sh@kde-coder.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Split KDE packages?
Date: Tue, 28 Jan 2003 04:57:44 +0100 [thread overview]
Message-ID: <200301280457.47708.sh@kde-coder.de> (raw)
In-Reply-To: <200301271908.14467.absinthe@pobox.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
On Tuesday 28 January 2003 01:08, Dylan Carlson wrote:
> On Monday 27 January 2003 06:42 pm, Jan Winhuysen wrote:
> > Hello everyone!
> > Is there a future plan to split the kde source packages into ebuilds for
> > single applications? Debian had this once, when it was on my box. I
> > think this would be a good idea, but I don't have the know-how to do
> > it...
>
> It's all done via Makefiles in the source distribution mostly. Getting
> this solved is a matter of convincing some people that this issue matters
> to enough users, and in turn finding the right way to put it in.
>
> Cervisia is (afaik) the only thing that exists independently of any KDE
> bundle at this moment.
>
> Please refer to the existing bug on this issue. Please add your comments
> and CC: yourself to it.
>
> http://bugs.gentoo.org/show_bug.cgi?id=11123
I don't think this is a good idea.
On RedHat distribution you got this foolish system (of course binary
packages).
You don't know which application is in the normal kde distribution or just a
plain application like whatever.
If you see kde as one complete desktop enviroment, then you let kde as is
(compiling all applications in one package the same time), there aren't a lot
of patches for kde in the last few months, so we can live with it as is.
regards,
\sh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+Nf+7V8AnusWiV6wRAr3RAKDOscWdRsT7AekHSNFpNqNseuUMUwCgxqNF
RdUp+eaNzh+5z8uXWwrhoXs=
=VFeK
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-28 4:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 23:42 [gentoo-dev] Split KDE packages? Jan Winhuysen
2003-01-28 0:08 ` Dylan Carlson
2003-01-28 3:57 ` Stephan Hermann [this message]
2003-01-28 4:13 ` Riyad Kalla
2003-01-28 10:34 ` Dylan Carlson
2003-01-28 10:56 ` Jan Winhuysen
2003-01-28 13:40 ` Riyad Kalla
2003-01-28 14:08 ` Marko Mikulicic
2003-01-28 14:32 ` Dylan Carlson
2003-01-28 14:44 ` Dylan Carlson
2003-01-28 14:24 ` Jan Winhuysen
2003-01-28 15:27 ` Stephan Hermann
2003-01-28 16:43 ` Dylan Carlson
2003-01-29 14:15 ` Dan Armak
2003-01-29 14:30 ` Dylan Carlson
2003-01-29 14:38 ` Riyad Kalla
2003-01-29 15:09 ` Dan Armak
2003-01-29 15:34 ` Dylan Carlson
2003-01-29 21:24 ` John Nilsson
2003-01-30 9:13 ` Stephan Hermann
2003-01-30 10:25 ` John Nilsson
2003-01-30 13:11 ` Dan Armak
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=200301280457.47708.sh@kde-coder.de \
--to=sh@kde-coder.de \
--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