On Fri, 13 Feb 2009 23:53:51 +0000
Ciaran McCreesh <[email protected]> wrote:

> On Sat, 14 Feb 2009 00:46:54 +0100
> Luca Barbato <[email protected]> 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: signature.asc
Description: PGP signature

Reply via email to