public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Live source based ebuild proposals
Date: Fri, 13 Feb 2009 19:19:23 -0600	[thread overview]
Message-ID: <20090213191923.7fb35b94@halo.dirtyepic.sk.ca> (raw)
In-Reply-To: 20090213235351.381cffcd@snowmobile

[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]

On Fri, 13 Feb 2009 23:53:51 +0000
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:

> On Sat, 14 Feb 2009 00:46:54 +0100
> Luca Barbato <lu_zero@gentoo.org> wrote:
> > master is just a name, you may have the main development happen in 
> > another branch (say devel) and the stabler tree is kept on the
> > master branch and you may want to track both as well.
> > 
> > Or even worse, you get two lines of development you want to track
> > that stay in completely different vcs. And that is the case of a
> > real package, not theory. In those cases having a template could
> > help a bit, having -scm + useflag is exactly the same as having bare
> > useflags and slots.
> 
> Yes, sometimes upstreams are insane. Then we can't deal with them.
> We're aiming to handle the large majority of sensible cases here, not
> the things that don't map onto version concepts in any way.
> 
> > >> Then if you continued to read you'll notice that
> > > 
> > > ...you got so incoherent I gave up trying to work out what you're
> > > on about. You still haven't shown how to solve the simple example
> > > I gave earlier in the thread.
> > 
> > Relying to offense because I just pointed out something you
> > dislikes since you cannot find a argumentative way reply isn't
> > exactly polite or mature.
> 
> No. Really. Again. You've been steadily talking nonsense on this whole
> issue. Please step back, start again and clearly and concisely explain
> in coherent English how you solve the simple example I gave earlier in
> the thread. I am far from the only person who hasn't managed to work
> out your explanation of this simple case so far.

I'm sorry, Luca, but I can't do what I want to do with your proposal.
With the -scm suffix I can.

Actually I thought this was settled.  What exactly is the issue holding
GLEP 54 back that we need more discussion and different proposals?


-- 
gcc-porting,                                      by design, by neglect
treecleaner,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-14  1:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090212214925.GA21532@dodo.hsd1.nj.comcast.net>
     [not found] ` <20090213155445.GA31550@dodo.hsd1.nj.comcast.net>
     [not found]   ` <4995ABE2.4000907@gentoo.org>
     [not found]     ` <20090213172725.34258824@snowcone>
     [not found]       ` <4995CB0B.80209@gentoo.org>
     [not found]         ` <20090213194141.24d44a37@snowcone>
2009-02-13 20:29           ` [gentoo-dev] Live source based ebuild proposals Was: [gentoo-council] Council log and summary for meeting on 02/12/09 Luca Barbato
2009-02-13 20:37             ` [gentoo-dev] " Ciaran McCreesh
2009-02-13 22:17               ` [gentoo-dev] Re: Live source based ebuild proposals Luca Barbato
2009-02-13 22:22                 ` Ciaran McCreesh
2009-02-13 22:35                   ` Luca Barbato
2009-02-13 22:52                     ` Ciaran McCreesh
2009-02-13 23:46                       ` Luca Barbato
2009-02-13 23:53                         ` Ciaran McCreesh
2009-02-14  1:19                           ` Ryan Hill [this message]
2009-02-14  2:57                             ` Duncan
2009-02-14 13:46                             ` Luca Barbato
2009-02-14  2:28                           ` Duncan
2009-02-14 14:41                           ` Luca Barbato
2009-02-15  8:05                             ` Duncan
2009-02-15 10:55                             ` Luca Barbato
2009-02-14  2:38                   ` Duncan

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=20090213191923.7fb35b94@halo.dirtyepic.sk.ca \
    --to=dirtyepic@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