From: Geert Bevin <gbevin@theleaf.be>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuilds for kde3 beta etc.
Date: Tue, 25 Dec 2001 21:40:05 +0100 [thread overview]
Message-ID: <3C28E425.6000903@theleaf.be> (raw)
In-Reply-To: 1009311584.8850.0.camel@zoidberg
> The ebuilds in /incoming are untested and should not be used by users.
> But since it's available to users, users use it anyway.
>
> I think it all comes down to what kind of distribution we want to
> create. If we want to make a distribution for those that create it and
> use-at-own-risk for everyone else (this is all fine by me) we should
> clearly state this (to users and developers).
Personally I think that since we're steering towards v1.0, stability and
clarity for the regular user should be an important issue. People tend
to ignore warnings or disclaimers and go ahead anyway. Then when it
doesn't work they either get a bad image of the distribution or they ask
questions on the mailinglist or irc channel about the stuff that was
essentially unsupported, taking up valuable developer's time and
patience. I really think that they shouldn't get the opportunity to get
access to those ebuilds unless it's clearly distributed seperately as a
complete alpha (or beta) branch. Just my idea on the topic.
> If we want to create a distributions for everyone we have to go around
> to make users don't hurt themeselfs. Since users _will_ do bad things to
> there own systems if they are able to. And if so, masking and comments
> are not enough, imho.
I agree with that.
> CVS branches solves these problems (and we have to start using branches
> sooner or later anyway, preferable when we release 1.0).
>
> Regards,
> Mikael Hallendal
--
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-25 20:40 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 [this message]
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=3C28E425.6000903@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