On Fri, 13 Jun 2008 10:43:39 +0200 Luca Barbato <[EMAIL PROTECTED]> wrote: > Ciaran McCreesh wrote: > > On Thu, 12 Jun 2008 21:40:28 +0200 > > Luca Barbato <[EMAIL PROTECTED]> wrote: > >>> * ordering for _pre is wrong. > >> hm? > > > > foo-0.26-live would become foo-0.26_pre1, which would be < 0.26. > > This is clearly wrong. > > No, it is correct and what you want. Upstream is aiming for 0.26, > once 0.26 gets in portage you want to update to the release.
A lot of projects work like this:
* trunk/ is current development, and is ahead of any release.
* branches/0.26/ is forked from trunk/ when 0.26 is released, and is
equal to or ahead of any 0.26 release.
How does your proposal handle this?
> >>> * How are you planning to handle reinstalls? Should installing
> >>> world always reinstall live things? Never? Or what?
> >> depends on the other ebuilds
> >
> > More specifically?
>
> the live ebuild act as template for a autogenerated _pre, if there is
> something higher than _pre that one will be picked.
So you install foo-1.2-live. The package manager installs this as
foo-1.2_pre1. Then, foo-1.2-live becomes foo-1.2_pre2.
Which has two issues:
* It means whenever you install foo-1.2-live, there will always be a
newer version, and the package manager will always select it for
upgrades. Is this really desired behaviour?
* It means the package manager somehow has to keep track of what pre to
substitute in. How does it do this?
>
> >>> * How are live ebuilds selected by the package manager?
> >> live ebuilds gets considered as preN+1 for any purpose.
> >
> > So you're saying they *always* get reinstalled as a new version if
> > they're part of the dep tree?
>
> only on -e since you do not have the live template evaluated again.
So when are templates evaluated?
> >>> * What's the filename for "live ebuild for SVN trunk/"? What about
> >> foo-${version inside trunk}.live?
> >
> > And when trunk is unversioned?
>
> Upstream has an issue, still you know which is the version they aim.
Again, no. It's fairly common for unversioned trunk where upstream
don't yet know if it'll be released as an x release, an x.y release or
an x.y.z release.
> >>> "live ebuild for SVN branches/0.26/"?
> >> foo-0.26.live?
> >
> > Orders incorrectly when 0.26.1 has been released.
>
> no.
Yup, because your 0.26 branch will be equal to or ahead of 0.26.1, but
0.26.live will order as less than 0.26.
> Anyway pkgcore and portage devs, I'd like your opinion on this point.
What, the gaping holes I've pointed out aren't enough?
--
Ciaran McCreesh
signature.asc
Description: PGP signature
