Date: Sun, 9 Feb 2020 16:06:01 +0200
From: Timo Teras <timo.teras@iki.fi>
To: Clayton Craft <clayton@craftyguy.net>
Cc: ~alpine/apk-tools@lists.alpinelinux.org
Subject: Re: supporting multiple versions of same package in single repo
Message-ID: <20200209160555.144c01f9@vostro.wlan>
In-Reply-To: <20200209023706.rizdc3333ljjjrie@computer.craftyguy.net>
References: <20200203222821.wty53efr5u2sx3gk@computer.craftyguy.net>
	<20200204110646.2d9f80b4@vostro>
	<20200209023706.rizdc3333ljjjrie@computer.craftyguy.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sat, 8 Feb 2020 18:37:06 -0800
Clayton Craft <clayton@craftyguy.net> wrote:

> On Tue, Feb 04, 2020 at 11:06:52AM +0200, Timo Teras wrote:
> >Interesting setup. I wonder if in Arch it is a feature where a global
> >substitution rule diverts mesa-dev to mesa-git-dev or similar.
> >
> >Using purely apk dependencies, you could try the following:
> >
> >1. mesa-git-dev
> >  provides="mesa-dev"
> >  provider_priority=1
> >
> >  The provides tells it's good for 'mesa-dev'. Since there's no
> > provided version specified it's not good for automatic install; the
> >  provider_priority=1 makes that happen.
> >
> >  One caveat is at least that if someone depends e.g
> > "mesa-dev>19.0", it would not get satisfied with the mesa-git-dev.
> >
> >  OR
> >
> >  provides="mesa-dev=19.2"
> >
> >  To make the git act as if it was this version. You probably then
> > want a smaller version than what the real mesa is so that the
> > mesa-git-dev does not get preferred always.  
> 
> Hmm, I think either option could cause issues. The first option is an
> issue because there do seem to be some packages that depend on
> 'mesa-dev>=19.3'. With the second option, some packages would pull in
> mesa-dev if they depended on a version greater than what is set in
> mesa-git-dev's "provides".
> 
> When apk is faced with two packages that 'provide' a virtual package
> (e.g. 'mesa' vs 'mesa-git'), and 'provider_priority' is not set in
> either one, what breaks the tie? Is it the one with the higher
> version (assuming one is specified in the 'provides=')?
> 
> >
> >2. mesa-git
> >  depends="!mesa"  
> 
> I was attempting to test this, but apk complains:
> (2363538) [18:28:58] ERROR: Package '!mesa': Could not find aport,
> and could not find this package in any APKINDEX!
> 
> >
> >  To make sure that depending on 'mesa-dev' does not prefer the real
> >  package and try to pull in it's dependencies.
> >
> >Interesting to hear if the above works.

If you are using separate repositories of which only one get's picked
up (or even if just the mesa-git providing repository is additional),
you can just have each mesa-git-* package provides="mesa-*=$pkgver"
where $pkgver should compare to something grater than the regular mesa.

Timo