Re: package locally compiled gets "upgraded"
On 03.06.09 10:34, Sven Joachim wrote:
> On 2009-06-03 09:23 +0200, Andrei Popescu wrote:
>
> > On Wed,03.Jun.09, 01:25:19, Matus UHLAR - fantomas wrote:
> >> On 02.06.09 14:29, Boyd Stephen Smith Jr. wrote:
> >> > In <[🔎] 20090602185609.GA26122@fantomas.sk>, Matus UHLAR - fantomas wrote:
> >> > >is 1.2.3lenny1 more than 1.2.3local1? I would want that to get upgraded...
> >> >
> >> > No. 1.2.3lenny1 < 1.2.3local1 because "lenny" < "local" because 'e' < 'o'.
> >>
> >> so iif I name it 'local0' and 'lenny1' comes out, it won't be installed
> >> because the version number is smaller.
>
> True, therefore it is prudent to use a local version that sorts before
> "lenny1", e.g. "custom1".
so I have to hope that one version of debian won't be called e.g. "aachen"
because I'd need local versions starting like "aaa" or "a~"
> > I think the correct way is to *append* to the version, not munge it:
> >
> > 1.2.3lenny1+local1 (I like to use + as separator)
>
> This will not work if the original version is 1.2.3, because
> 1.2.3+local1 > 1.2.3lenny1 (the version for potential security updates).
seems the only thing I can do now is hope that updates will be called
"lenny*" so I'm limited in naming the local version...
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Fighting for peace is like fucking for virginity...
Reply to: