From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for how to handle stable ebuilds
Date: Mon, 10 Nov 2008 20:23:42 +0200 [thread overview]
Message-ID: <1226341422.16453.3.camel@localhost> (raw)
In-Reply-To: <20081110181334.GD7038@aerie.halcy0n.com>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
On E, 2008-11-10 at 13:13 -0500, Mark Loeser wrote:
> Removing Stable Ebuilds
>
> If an ebuild meets the time criteria above, and there are no technical issues
> preventing stabilization, then the maintainer MAY choose to delete an older
> version even if it is the most recent stable version for a particular arch.
Even if that is a package that other packages depend on? Lets say I want
to delete an ancient version of gtk+, but arch ABC has that as the only
stable ebuild, while the rest are ~ABC. Do I remove it, as I may, and
break the whole stable tree of arch ABC, unkeyword hundreds of other
packages, or I'm just allowed to remove it but should really apply a
common sense as usual and you don't want to go into details in this
document?
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-10 18:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 18:13 [gentoo-dev] Proposal for how to handle stable ebuilds Mark Loeser
2008-11-10 18:23 ` Ciaran McCreesh
2008-11-10 18:23 ` Mart Raudsepp [this message]
2008-11-10 20:32 ` Steev Klimaszewski
2008-11-10 21:16 ` Jeremy Olexa
2008-11-10 21:57 ` Santiago M. Mola
2008-11-11 0:24 ` Jose Luis Rivero
2008-11-11 1:13 ` Mark Loeser
2008-11-11 9:31 ` Jose Luis Rivero
2008-11-11 1:21 ` Richard Freeman
2008-11-11 8:56 ` Peter Volkov
2008-11-11 10:18 ` Jose Luis Rivero
2008-11-11 13:49 ` Ferris McCormick
2008-11-11 16:06 ` [gentoo-dev] " Duncan
2008-11-11 16:24 ` Jeroen Roovers
2008-11-11 17:26 ` Duncan
2008-11-11 17:55 ` Ferris McCormick
2008-11-11 18:12 ` Jeroen Roovers
2008-11-11 21:03 ` Duncan
2008-11-13 17:38 ` [gentoo-dev] " Tobias Scherbaum
2008-11-15 13:02 ` Matti Bickel
2008-11-17 18:08 ` Tobias Scherbaum
2008-11-17 19:03 ` [gentoo-dev] " Duncan
2008-12-11 5:35 ` [gentoo-dev] " Donnie Berkholz
2008-11-17 0:38 ` [gentoo-dev] " Ryan Hill
2008-11-17 15:10 ` Daniel Gryniewicz
2008-11-18 1:08 ` Ryan Hill
2008-11-18 16:57 ` Daniel Gryniewicz
2008-11-18 17:50 ` Ciaran McCreesh
2008-11-18 20:31 ` Daniel Gryniewicz
2008-11-18 21:18 ` Ryan Hill
2008-11-18 22:04 ` Daniel Gryniewicz
2008-11-18 22:45 ` Ryan Hill
2008-11-30 22:59 ` Ryan Hill
2008-12-01 7:49 ` Peter Volkov
2008-12-11 5:37 ` [gentoo-dev] " Donnie Berkholz
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=1226341422.16453.3.camel@localhost \
--to=leio@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