From: "Nirbheek Chauhan" <nirbheek.chauhan@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [GLEP] scm package version suffix
Date: Tue, 11 Dec 2007 17:40:00 +0530 [thread overview]
Message-ID: <8b4c83ad0712110410y2f773548kfb0ec5dd3e1e057e@mail.gmail.com> (raw)
In-Reply-To: <20071211111729.0ab60df6@blueyonder.co.uk>
On Dec 11, 2007 4:47 PM, Ciaran McCreesh
<ciaran.mccreesh@blueyonder.co.uk> wrote:
> On Tue, 11 Dec 2007 16:36:51 +0530
> "Nirbheek Chauhan" <nirbheek.chauhan@gmail.com> wrote:
> > The idea is that no one would want to automatically upgrade to a
> > branch (because you cannot define "upgrade" for branches), so make it
> > manual.
>
> ...and this is why branches shouldn't be treated like versions. They
> have their own set of rules and expected behaviours that are best dealt
> with by a different proposal.
I made that statement in the context of unversioned branches where you
do not know when the branch will be merged. In the case where you do
know when the branch will be merged, the versioned branch ebuild can
easily be included in the upgrade list via it's version.
So, you cannot "upgrade" to app-misc/foo-scm_bblah but you *can*
upgrade from app-misc/foo-1.2 to app-misc/foo-1.2-scm_bblahblah and
then finally upgrade to app-misc/foo-1.3 when the branch gets merged.
--
~Nirbheek Chauhan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-12-11 12:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 16:01 [gentoo-dev] [GLEP] scm package version suffix Piotr Jaroszyński
2007-12-09 16:18 ` Josh Sled
2007-12-09 17:22 ` Piotr Jaroszyński
2007-12-09 17:52 ` Petteri Räty
2007-12-09 18:00 ` Piotr Jaroszyński
2007-12-09 18:45 ` Jan Kundrát
2007-12-09 18:57 ` Ciaran McCreesh
2007-12-10 4:31 ` Donnie Berkholz
2007-12-10 7:18 ` Ciaran McCreesh
2007-12-10 7:44 ` Nirbheek Chauhan
2007-12-10 8:24 ` Ciaran McCreesh
2007-12-10 8:36 ` Robin H. Johnson
2007-12-10 8:44 ` Ciaran McCreesh
2007-12-11 1:12 ` [gentoo-dev] " Ryan Hill
2007-12-10 12:59 ` [gentoo-dev] " Robert Buchholz
2007-12-10 14:24 ` Nirbheek Chauhan
2007-12-10 15:14 ` Robert Buchholz
2007-12-10 19:44 ` Nirbheek Chauhan
2007-12-10 19:49 ` Nirbheek Chauhan
2007-12-11 0:27 ` [gentoo-dev] " Steve Long
2007-12-11 10:59 ` Nirbheek Chauhan
2007-12-11 11:03 ` Nirbheek Chauhan
2007-12-11 8:21 ` Duncan
2007-12-11 11:06 ` Nirbheek Chauhan
2007-12-11 11:17 ` Ciaran McCreesh
2007-12-11 12:10 ` Nirbheek Chauhan [this message]
2007-12-10 8:26 ` [gentoo-dev] " Robin H. Johnson
2007-12-10 8:34 ` Ciaran McCreesh
2007-12-10 9:21 ` [gentoo-dev] Handling branch strings Donnie Berkholz
2007-12-10 9:34 ` Santiago M. Mola
2007-12-10 19:42 ` Donnie Berkholz
2007-12-11 1:35 ` [gentoo-dev] " Ryan Hill
2007-12-11 8:11 ` [gentoo-dev] " Ciaran McCreesh
2007-12-11 11:46 ` Santiago M. Mola
2007-12-11 17:56 ` [gentoo-dev] " Christian Faulhammer
2007-12-09 19:38 ` [gentoo-dev] Re: [GLEP] scm package version suffix Ryan Hill
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=8b4c83ad0712110410y2f773548kfb0ec5dd3e1e057e@mail.gmail.com \
--to=nirbheek.chauhan@gmail.com \
--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