RE: Maintaing an aptable archive with a potato - woody mixture
>
> Is there any way to keep a new debian/$PACKAGE_foo++.deb from
> overriding
> $COMPANY/$PACKAGE_foo.deb?
>
Your second idea will definately be easier to maintain long term. We do this
at va as well.
As for taking woody packages and placing them in potato, the usual numbering
scheme is:
is foo_1.2-3.deb is from woody it becomes foo_1.2-0potato3.deb. The 3 is the
old version from woody, the 0 is whatever the new one for potato should be.
Any time you see this versioning scheme, you know the package is a backport.
Security does this currently. If you MUST ensure the your package is used, a
epoch is the strongest solution. 1:1.2 will be newer than 1.2, 1.3, etc. Only
another epoched package could override it. Disadvantage is you have to use
epochs for as long as that package lives. otherwise something like
foo_1.2-13potato3.deb will almost always win. You could also use
1.2-0<company>3, if you like, to know that the package installed you made.
Reply to: