public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Re: Comparison of GLEP 54 and 'live ebuild' proposal
Date: Wed, 11 Mar 2009 17:12:15 +0100	[thread overview]
Message-ID: <49B7E2DF.60805@gentoo.org> (raw)
In-Reply-To: <20090311154416.2f79324c@snowcone>

Ciaran McCreesh wrote:
> On Wed, 11 Mar 2009 16:20:25 +0100
> Luca Barbato <lu_zero@gentoo.org> wrote:
>>>> [ebuild     U ] sys-devel/gcc-4.4.0_pre20090310 [from svn master
>>>> r12345]
>>> That claim right there is enough to show that you haven't thought
>>> about this at all. Your proposal is lots of handwaving magic, most
>>> of it unimplementable. I suggest you put together a reference
>>> implementation before promoting this idea any further.
>> What's wrong is U that should be R beside that there isn't much
>> magic...
> 
> The U isn't the problem. The svn revision is the problem. You need to
> consider how the package manager would get the revision.
> 

I know, if you are re emerging you have those information, if you are 
updating you won't have them. That's why either the U or the revision 
information is wrong.

lu

-- 

Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero




  reply	other threads:[~2009-03-11 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  5:42 [gentoo-council] Re: Comparison of GLEP 54 and 'live ebuild' proposal Ryan Hill
2009-03-11  9:55 ` Luca Barbato
2009-03-11 14:13   ` Ciaran McCreesh
2009-03-11 15:20     ` Luca Barbato
2009-03-11 15:44       ` Ciaran McCreesh
2009-03-11 16:12         ` Luca Barbato [this message]
2009-03-11 15:18   ` Alec Warner
2009-03-12  3:55   ` Ryan Hill
2009-03-12 13:56     ` Luca Barbato

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=49B7E2DF.60805@gentoo.org \
    --to=lu_zero@gentoo.org \
    --cc=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-council@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