From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuilds for kde3 beta etc.
Date: 26 Dec 2001 05:10:11 +0100 [thread overview]
Message-ID: <1009339812.8850.10.camel@zoidberg> (raw)
In-Reply-To: <20011225213330.E17475@chiba.3jane.net>
[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]
ons 2001-12-26 klockan 04.33 skrev Daniel Robbins:
> Just remember that we have to somehow work towards a *stable* KDE3 release. I
> think having a separate system profile for KDE3 development might be a good
> compromise.
Ok, looks like you misunderstood me. I'm not talking about beta
_ebuilds_. I'm talking about beta packages (like for instance, GNOME
produces lots of beta releases of GNOME2. These packages are _only_
supposed for GNOME developers). From my discussion with Dan about this
issue, the KDE3 betas we are discussing here are for KDE developers.
Beta ebuilds are a totally different issue. In that case I think masking
them is the correct way to go. But if we start packaging stuff that we
know are very unstable packages we'll end up spending lots of time on
doing:
*) Patches for the installations (since it's not finished) which is
obsoleted when the stable version comes out.
*) Debugging KDE/foobar source which has nothing to do with Gentoo.
*) Having to spend lots of time trying to figure out if it's our ebuilds
or the released tarballs that is flaky.
And trust me, we will end up doing all of the above, no matter how many
warning signs we put up. Because most people takes a look on them and
thinks it's ok. Then they will mail the mailinglist or discuss on IRC
never the less and the developers will end up spending lots of time on
these things that is none of Gentoo's concern.
So what I'm saying is that _we_ shouldn't work towards a stable KDE3
release, the KDE release team should. Once it's out we should work
towards stable packages of that software.
This is why I suggested to Dan that if he wants to play around with KDE3
he should make ebuilds and distribute them from himself rather than in
the portage. That way it will be clear that users wanting to discuss
KDE3/those ebuilds should turn to him rather than any of the other
developers.
This is the way I plan to distribute ebuilds for Gtk+/GNOME pre-2.0.
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-26 4:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 16:57 [gentoo-dev] ebuilds for kde3 beta etc Dan Armak
2001-12-22 17:28 ` Daniel Robbins
2001-12-22 18:00 ` Dan Armak
2001-12-22 18:29 ` Guido Bakker
2001-12-22 18:12 ` Dan Armak
2001-12-23 13:44 ` Mikael Hallendal
2001-12-23 14:07 ` Dan Armak
2001-12-23 23:08 ` Mikael Hallendal
2001-12-24 0:36 ` Daniel Robbins
2001-12-24 8:27 ` Geert Bevin
2001-12-25 1:12 ` Mikael Hallendal
2001-12-25 5:00 ` Dan Armak
2001-12-25 5:11 ` Daniel Robbins
2001-12-25 12:10 ` Mikael Hallendal
2001-12-25 15:49 ` Daniel Robbins
2001-12-25 20:19 ` Mikael Hallendal
2001-12-25 20:40 ` Geert Bevin
2001-12-26 1:47 ` Daniel Robbins
2001-12-26 2:14 ` Mikael Hallendal
2001-12-26 2:44 ` Daniel Robbins
2001-12-26 3:01 ` Mikael Hallendal
2001-12-26 3:33 ` Daniel Robbins
2001-12-26 4:10 ` Mikael Hallendal [this message]
2001-12-26 5:43 ` Daniel Robbins
2001-12-26 6:39 ` Dan Armak
2001-12-26 6:51 ` Mikael Hallendal
2001-12-26 6:56 ` Joshua Pierre
2001-12-27 19:41 ` Damon M. Conway
2001-12-26 5:16 ` Joshua Pierre
2001-12-26 1:51 ` Daniel Robbins
2001-12-24 9:59 ` Guido Bakker
2001-12-24 12:11 ` Sebastian Werner
2001-12-24 13:38 ` Dan Armak
2001-12-25 1:14 ` Mikael Hallendal
2001-12-23 14:13 ` Dan Armak
2001-12-26 9:34 ` Dan Armak
2001-12-26 9:37 ` Dan Armak
2001-12-26 13:46 ` Bart Verwilst
2001-12-26 16:50 ` Daniel Robbins
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=1009339812.8850.10.camel@zoidberg \
--to=hallski@gentoo.org \
--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