From: Luca Barbato <lu_zero@gentoo.org>
To: Thomas Anderson <gentoofan23@gentoo.org>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Comparison of GLEP 54 and 'live ebuild' proposal
Date: Tue, 10 Mar 2009 03:26:39 +0100 [thread overview]
Message-ID: <49B5CFDF.3050006@gentoo.org> (raw)
In-Reply-To: <20090309224725.GA11724@dodo.hsd1.nj.comcast.net>
Thomas Anderson wrote:
> Hi,
>
> Attached is my comparison of the two proposals for live sources.
> Sorry about getting it out late, I had to get ahold of a number of
> people to finish writing it up.
I'd be happier if you actually provided it with a better description
and/or updated drafts along.
The glep54 doesn't state anything about how/where the specific revision
is stored nor what the live property is and it implicitly
provides/triggers in the package manager.
The main technical objection could be stated as "does nothing beside
giving a token to describe infinity for a version component as version
suffix".
The actual draft for the live templates is present at
http://dev.gentoo.org/~lu_zero/glep/liveebuild.rst
And should cover the concern you raised here beside the following
> Similar to the above problem is what occurs when a user understandably
> puts =media-tv/mythtv-0.20_20090301 in package.{use,keywords} and the
> date changes. Also, what happens if the user
> =media-tv/mythtv-0.20.live in package.{use,keywords}? Is live expanded
> that early so it is invalid or is it still valid?
Having =cat/pkg-ver.live in package.{use, keywords} would translate to a
sort of =cat/pkg-ver* but would be nicer putting directly an isodate to
restrict better what you want in and what you want out.
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
next prev parent reply other threads:[~2009-03-10 2:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 22:47 [gentoo-council] Comparison of GLEP 54 and 'live ebuild' proposal Thomas Anderson
2009-03-09 23:29 ` Roy Bamford
2009-03-10 1:15 ` Thomas Anderson
2009-03-10 1:53 ` Luca Barbato
2009-03-10 2:26 ` Luca Barbato [this message]
2009-03-10 14:00 ` Thomas Anderson
2009-03-10 14:39 ` Thomas Anderson
2009-03-10 14: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=49B5CFDF.3050006@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
--cc=gentoofan23@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