Re: [gentoo-portage-dev] Latest version vs specific version

2005-12-15 Thread Andrea Carpani
Il giorno sab, 03-12-2005 alle 21:23 +0900, Jason Stubbs ha scritto:


> Not really necessary. He has an ebuild that says "=kde-3.4.0* =xorg-x11-6.7*" 
> which pulls in kde first which then pulls in "xorg-x11" which portage 
> resolves to xorg-x11-6.8 after which portage processes xorg-x11-6.7* to 
> xorg-x11-6.7 and both versions get installed (the latter overwriting the 
> former and causing the former to be unmerged). It's essentially bug 1343.

Yes, thanks.
It looks like my problem is the same as described in bug 1343.


-- 
Andrea Carpani <[EMAIL PROTECTED]>

-- 
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] Latest version vs specific version

2005-12-03 Thread Marius Mauch

Jason Stubbs wrote:

On Saturday 03 December 2005 13:27, Marius Mauch wrote:


Andrea Carpani wrote:


...
and I have binary packages for both c-4.0 and c-4.1 when I emerge
virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get
both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a
dep for a-2.0 who gets the latest c even though c-4.0 would have
satisfied the dependency.

Any info on how to avoid this?


It might be helpful if you'd post a real example and not some invalid
pseudo-ebuild syntax.



Not really necessary. He has an ebuild that says "=kde-3.4.0* =xorg-x11-6.7*" 
which pulls in kde first which then pulls in "xorg-x11" which portage 
resolves to xorg-x11-6.8 after which portage processes xorg-x11-6.7* to 
xorg-x11-6.7 and both versions get installed (the latter overwriting the 
former and causing the former to be unmerged). It's essentially bug 1343.


Hmm, you must have seen more than I did then as I couldn't spot any atom 
in the mail. Or you're just better at guessing ;)


Marius
--
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] Latest version vs specific version

2005-12-03 Thread Jason Stubbs
On Saturday 03 December 2005 13:27, Marius Mauch wrote:
> Andrea Carpani wrote:
> > ...
> > and I have binary packages for both c-4.0 and c-4.1 when I emerge
> > virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get
> > both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a
> > dep for a-2.0 who gets the latest c even though c-4.0 would have
> > satisfied the dependency.
> >
> > Any info on how to avoid this?
>
> It might be helpful if you'd post a real example and not some invalid
> pseudo-ebuild syntax.

Not really necessary. He has an ebuild that says "=kde-3.4.0* =xorg-x11-6.7*" 
which pulls in kde first which then pulls in "xorg-x11" which portage 
resolves to xorg-x11-6.8 after which portage processes xorg-x11-6.7* to 
xorg-x11-6.7 and both versions get installed (the latter overwriting the 
former and causing the former to be unmerged). It's essentially bug 1343.

--
Jason Stubbs
-- 
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] Latest version vs specific version

2005-12-02 Thread Marius Mauch

Andrea Carpani wrote:
Hi all. Here's my problem. 


I'm using a lot binary packages of "in portage" and "custom created"
ebuilds. I have a "virtual" ebuild I use that contains only dependencies
and I use this one to merge given versions of packages all in one shot:
sort of a shanpshot of a given moment in time (sort of tag).

Eg:

virtual-1.0.ebuild contains

RDEPEND="
a-2.0.ebuild
b-3.0.ebuild
c-4.0.ebuild
d-5.0.ebuild
"

So that emerge -K virtual-1.0 emerges all a,b,c,d on given versions and:

virtual-2.0.ebuild contains

RDEPEND="
a-2.1.ebuild
b-3.1.ebuild
c-4.1.ebuild
d-5.1.ebuild
"

My problem is that if a-2.0.ebuild and a-2.1.ebuild contain

RDEPEND="


c-1.0


"

and I have binary packages for both c-4.0 and c-4.1 when I emerge
virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get
both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a
dep for a-2.0 who gets the latest c even though c-4.0 would have
satisfied the dependency.

Any info on how to avoid this?


It might be helpful if you'd post a real example and not some invalid 
pseudo-ebuild syntax.


Marius
--
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] Latest version vs specific version

2005-12-02 Thread Andrea Carpani
Il giorno ven, 02-12-2005 alle 15:57 +0100, Paul de Vrieze ha scritto:

> > Any info on how to avoid this?
> 
> It would a different planner component in portage.

Ok. So it's not possible at the time being?

Any idea on how to implement some sort of "virtual package" that
installs given versions of pagackes?

-- 
Andrea Carpani <[EMAIL PROTECTED]>

-- 
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] Latest version vs specific version

2005-12-02 Thread Paul de Vrieze
On Friday 02 December 2005 15:43, Andrea Carpani wrote:
> Hi all. Here's my problem.
>
> I'm using a lot binary packages of "in portage" and "custom created"
> ebuilds. I have a "virtual" ebuild I use that contains only
> dependencies and I use this one to merge given versions of packages all
> in one shot: sort of a shanpshot of a given moment in time (sort of
> tag).
>
> Eg:
>
> virtual-1.0.ebuild contains
>
> RDEPEND="
> a-2.0.ebuild
> b-3.0.ebuild
> c-4.0.ebuild
> d-5.0.ebuild
> "
>
> So that emerge -K virtual-1.0 emerges all a,b,c,d on given versions
> and:
>
> virtual-2.0.ebuild contains
>
> RDEPEND="
> a-2.1.ebuild
> b-3.1.ebuild
> c-4.1.ebuild
> d-5.1.ebuild
> "
>
> My problem is that if a-2.0.ebuild and a-2.1.ebuild contain
>
> RDEPEND="
>
> >c-1.0
>
> "
>
> and I have binary packages for both c-4.0 and c-4.1 when I emerge
> virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get
> both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a
> dep for a-2.0 who gets the latest c even though c-4.0 would have
> satisfied the dependency.
>
> Any info on how to avoid this?

It would a different planner component in portage.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: [EMAIL PROTECTED]
Homepage: http://www.devrieze.net


pgpS7KI6FTa4j.pgp
Description: PGP signature


[gentoo-portage-dev] Latest version vs specific version

2005-12-02 Thread Andrea Carpani
Hi all. Here's my problem. 

I'm using a lot binary packages of "in portage" and "custom created"
ebuilds. I have a "virtual" ebuild I use that contains only dependencies
and I use this one to merge given versions of packages all in one shot:
sort of a shanpshot of a given moment in time (sort of tag).

Eg:

virtual-1.0.ebuild contains

RDEPEND="
a-2.0.ebuild
b-3.0.ebuild
c-4.0.ebuild
d-5.0.ebuild
"

So that emerge -K virtual-1.0 emerges all a,b,c,d on given versions and:

virtual-2.0.ebuild contains

RDEPEND="
a-2.1.ebuild
b-3.1.ebuild
c-4.1.ebuild
d-5.1.ebuild
"

My problem is that if a-2.0.ebuild and a-2.1.ebuild contain

RDEPEND="
>c-1.0
"

and I have binary packages for both c-4.0 and c-4.1 when I emerge
virtual-2.0.ebuild i get c-4.1.ebuild but if I emerge virtual-1.0 I get
both c-4.0 (required as a dependency for virtual-1.0) and c-4.1 (as a
dep for a-2.0 who gets the latest c even though c-4.0 would have
satisfied the dependency.

Any info on how to avoid this?

-- 

[EMAIL PROTECTED]
http://www.carpani.net
Andrea Carpani
.a.c.

-- 
Andrea Carpani <[EMAIL PROTECTED]>

-- 
gentoo-portage-dev@gentoo.org mailing list