From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree
Date: Tue, 12 Jun 2007 11:59:28 +0200 [thread overview]
Message-ID: <466E6E80.2050603@gentoo.org> (raw)
In-Reply-To: <C29EC904-37E4-4487-97F6-46EB69DDD8AF@cilly.mine.nu>
cilly wrote:
> Hi all,
>
> I think it's worth to discuss the `behaviour of removing ebuilds from
> the tree`.
Currently it's up to the developer, some people are more conservative,
some prefer to get rid of certain stuff asap.
You should differentiate between ~ and stable ones btw...
>
> In my opinion, ebuilds are removed too soon, i.e. if an ebuild gets updated
> the older ebuild gets removed in the same turn.
This happens only when:
- there are security concerns
- the old ebuild was there till ages and the new one had been in ~ since
ages.
> In my opinion, it is better to keep the older ebuild around for a while since
> if there are some bugs in the newer ebuild, users are able to downgrade easily.
that's is quite up to the specific applications IMHO.
> What do you think?
I'd leave it up to the developer, nothing is lost in gentoo and fetching
from the attic isn't exactly difficult. Still probably having a note to
make people aware of that could be useful since the problem you pointed
doesn't require any more work to be solved.
> PS: other topics to be discussed `Not to modify ebuilds which are
> already in the tree... even if masked` what do you think?
I probably understood what you mean and well, no, I don't think is a
good idea.
lu - that prefers less rules and more people aware.
--
Luca Barbato
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-12 9:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 9:40 [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree cilly
2007-06-12 9:49 ` [gentoo-dev] " Christian Faulhammer
2007-06-12 9:53 ` cilly
2007-06-12 9:59 ` Luca Barbato [this message]
2007-06-12 10:04 ` [gentoo-dev] " Fernando J. Pereda
2007-06-12 10:01 ` Fernando J. Pereda
2007-06-12 10:14 ` cilly
2007-06-12 10:21 ` Fernando J. Pereda
2007-06-12 10:30 ` cilly
2007-06-12 10:40 ` Marijn Schouten (hkBst)
2007-06-12 10:48 ` cilly
2007-06-12 11:09 ` Marijn Schouten (hkBst)
2007-06-12 10:36 ` Richard Freeman
2007-06-12 10:46 ` Fernando J. Pereda
2007-06-12 10:53 ` cilly
2007-06-12 10:59 ` cilly
2007-06-12 11:27 ` Luca Barbato
2007-06-12 11:37 ` cilly
2007-06-12 11:29 ` Christoph Mende
2007-06-12 11:38 ` cilly
2007-06-13 14:35 ` Robert Buchholz
2007-06-13 14:58 ` Brian Harring
2007-06-12 16:55 ` [gentoo-dev] " Duncan
2007-06-13 14:44 ` banym tuxaner
2007-06-12 11:03 ` [gentoo-dev] " Fernando J. Pereda
2007-06-12 11:08 ` cilly
2007-06-12 16:05 ` Luis Francisco Araujo
2007-06-12 10:48 ` Luca Barbato
2007-06-12 10:50 ` cilly
2007-06-12 11:21 ` Petteri Räty
2007-06-12 11:50 ` cilly
2007-06-12 11:00 ` Marijn Schouten (hkBst)
2007-06-12 11:25 ` [gentoo-dev] " Christian Faulhammer
2007-06-12 11:52 ` cilly
2007-06-12 12:55 ` [gentoo-dev] " Marius Mauch
2007-06-12 12:59 ` cilly
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=466E6E80.2050603@gentoo.org \
--to=lu_zero@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