[haiku-commits] Re: haiku: hrev50069 - build/jam/repositories/HaikuPorts

  • From: Ingo Weinhold <ingo_weinhold@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 2 Feb 2016 10:56:35 +0100

On 01.02.2016 22:48, Axel Dörfler wrote:
> Am 01/02/2016 um 22:26 schrieb Ingo Weinhold:
>> On 01.02.2016 19:28, (Redacted sender humdingerb for DMARC) wrote:
>>> 66f815e0baa7: The yab package with a correct revision...
>>>    bbjimmy informed me the correct revision is "1" as otherwise it
>>>    would collide with the same package hosted on FatElk...
>> What does "collide" mean in this context? One repository really should
>> need to care about package revisions in another one.
> I guess there is a *NOT* missing :-)

Indeed. :-)

On 02.02.2016 08:28, Humdinger (Redacted sender humdingerb for DMARC) wrote:

On 1 February 2016 at 22:26, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
What does "collide" mean in this context? One repository really should need
to care about package revisions in another one.

I guess he worried that having the same package with different
revisions in two repositories could cause issues (maybe updating
unnecessarily or not at all?). I wasn't sure, so I figured, better
safe than sorry.
Feel free to elaborate why there's nothing to worry about. :)

AFAIK, if the packages have different vendor IDs the dependency and one of the packages is installed, the solver will usually try to stick with the same vendor for that package, even if the other version is newer. "Usually" because there are exceptions -- e.g. when the other package's version is greater and a package you request to install requires then greater version.

Anyway, the package revision is incremented whenever there is the need to do that, i.e. if the package built from the recipe differs from the previously built one (e.g. due to new patches or changes in the recipe that affect the package). It is necessary to do that so that the clients can actually recognize the new package as newer and update the installation.

CU, Ingo

Other related posts: