public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Anderson <gentoofan23@gentoo.org>
To: Roy Bamford <neddyseagoon@gentoo.org>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Comparison of GLEP 54 and 'live ebuild' proposal
Date: Mon, 9 Mar 2009 21:15:25 -0400	[thread overview]
Message-ID: <20090310011525.GA13732@dodo.hsd1.nj.comcast.net> (raw)
In-Reply-To: <1236641374.19203.0@spike>

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

On Mon, Mar 09, 2009 at 11:29:29PM +0000, Roy Bamford wrote:
> live can change several times a day. With only one day resolution, how 
> do you handle that?


Hi Roy,

   I'm not entirely sure you can handle that with liveebuild. In my opinion the correct
   thing to do is not to attempt to put the revision in the package
   version but to have it exposed in some other way(say a metadata
   variable holding the installed revision). Otherwise you're just going
   to end up trying to get more precise and more precise times.

   Really, you shouldnt be putting dates in place of revisions in the
   package version. It's just a bad idea.
-- 
---------
Thomas Anderson
Gentoo Developer
/////////
Areas of responsibility:
AMD64, Secretary to the Gentoo Council
---------

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

  reply	other threads:[~2009-03-10  1:15 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 [this message]
2009-03-10  1:53   ` Luca Barbato
2009-03-10  2:26 ` Luca Barbato
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=20090310011525.GA13732@dodo.hsd1.nj.comcast.net \
    --to=gentoofan23@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=neddyseagoon@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