From: Geert Bevin <gbevin@theleaf.be>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuilds for kde3 beta etc.
Date: Mon, 24 Dec 2001 09:27:39 +0100 [thread overview]
Message-ID: <3C26E6FB.6010600@theleaf.be> (raw)
In-Reply-To: 1009148900.708.2.camel@zoidberg
Mikael Hallendal wrote:
> I wasn't talking about just KDE, but if we put KDE in I can't see why we
> couldn't put all alpha-releases. And others might break things. So can
> KDE3 if it installs over other files (like pilot-link installing over
> glibc and stuff).
>
> And what I'm talking about here is not that the actual code is beta
> (since very much of what is in portage now is "beta"). I'm talking about
> beta-releases (which are only meant for developers of KDE/GNOME/foo,
> depending on what kind of packages it is).
Personally I'm not so hot either that these ebuilds would propagate to
every regular user. However, using cvs for developers to make it easy to
test the ebuilds is of course the best way to do so. Why not put them in
gentoo-src in a dedicated ebuild-beta directory. That way, the best of
both world are met. Another idea might be for rsync to filter out all
masked ebuilds. However I don't know if this would be possible. Starting
to branch the cvs into stable / development ebuilds seems a bit too much
of a hassle currently. After the release of 1.0 this might however be
the best way to proceed.
--
Geert Bevin
the Leaf sprl/bvba
"Use what you need" Pierre Theunisstraat 1/47
http://www.theleaf.be
1030 Brussels
gbevin@theleaf.be
Tel & Fax +32 2 241 19 98
next prev parent reply other threads:[~2001-12-24 8:28 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 [this message]
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
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=3C26E6FB.6010600@theleaf.be \
--to=gbevin@theleaf.be \
--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