]] Russ Allbery
> Dmitrii Kashin writes:
> > Josselin Mouette writes:
>
> >> In a Debian repository, there can be only one version of D at a time,
> >> so this cannot happen. If you want two versions of the same package in
> >> the same repository, they need to have different source and binary
Wouter Verhelst writes:
> On Tue, Jan 12, 2016 at 03:34:20PM +0100, Philip Hands wrote:
>> Josselin Mouette writes:
>>
>> > Dmitrii Kashin wrote:
>> >> The main thing is we can describe dependency as `pkg (= "2.0")' and yum
>> >> will
>> >> install package `pkg' of version "2.0" with the maxi
Dmitrii Kashin writes:
> Josselin Mouette writes:
>> In a Debian repository, there can be only one version of D at a time,
>> so this cannot happen. If you want two versions of the same package in
>> the same repository, they need to have different source and binary
>> names (the name can be som
On Tue, Jan 12, 2016 at 03:34:20PM +0100, Philip Hands wrote:
> Josselin Mouette writes:
>
> > Dmitrii Kashin wrote:
> >> The main thing is we can describe dependency as `pkg (= "2.0")' and yum
> >> will
> >> install package `pkg' of version "2.0" with the maximum revision
> >> found. And also
Lars Wirzenius writes:
> On Tue, Jan 12, 2016 at 05:58:48PM +0300, Dmitrii Kashin wrote:
>> Hm. It seems to be a solution. But I don't really understand how version
>> comparison works with symbols `.', `~' and `+'. Where can I read
>> comparison rules?
>
> This is the specification for version c
On Tue, Jan 12, 2016 at 05:58:48PM +0300, Dmitrii Kashin wrote:
> Hm. It seems to be a solution. But I don't really understand how version
> comparison works with symbols `.', `~' and `+'. Where can I read
> comparison rules?
This is the specification for version comparison rules in Debian:
https
Josselin Mouette writes:
> Dmitrii Kashin wrote:
>> The main thing is we can describe dependency as `pkg (= "2.0")' and yum will
>> install package `pkg' of version "2.0" with the maximum revision
>> found. And also we can write dependency specifically with revision,
>> f.e. `pkg (= "2.0-43")'
Josselin Mouette writes:
> Dmitrii Kashin wrote:
>> The main thing is we can describe dependency as `pkg (= "2.0")' and yum will
>> install package `pkg' of version "2.0" with the maximum revision
>> found. And also we can write dependency specifically with revision,
>> f.e. `pkg (= "2.0-43")' a
Dmitrii Kashin writes:
> There's an interesting type of dependencies in RPM: "non-strict equals".
>
> The main thing is we can describe dependency as `pkg (= "2.0")' and yum will
> install package `pkg' of version "2.0" with the maximum revision
> found. And also we can write dependency specifica
On Tue, Jan 12, 2016 at 02:20:38PM +0100, Josselin Mouette wrote:
> Dmitrii Kashin wrote:
> > If there's package A which depends on B and C, B depends on D (=
> > "2.0-43") and C depends on D (>= "2.0"). If there're packages D-2.0-43
> > and D-3.0 in the repository, then yum fails to resolve depen
Dmitrii Kashin wrote:
> The main thing is we can describe dependency as `pkg (= "2.0")' and yum will
> install package `pkg' of version "2.0" with the maximum revision
> found. And also we can write dependency specifically with revision,
> f.e. `pkg (= "2.0-43")' and yum will install specifically
There's an interesting type of dependencies in RPM: "non-strict equals".
The main thing is we can describe dependency as `pkg (= "2.0")' and yum will
install package `pkg' of version "2.0" with the maximum revision
found. And also we can write dependency specifically with revision,
f.e. `pkg (= "
12 matches
Mail list logo
