Re: udeb version tracking
Sebastian Ley <sebastian.ley@mmweg.rwth-aachen.de> writes:
> Am Di, den 18.11.2003 schrieb Geert Stappers um 11:15:
>
> > > Well, udpkg does not even handle versioned Depends... So as the
> > > situation is now we do only care about names. Hence my proposal would
> > > work. However we should investigate if it would be a good idea to
> > > implement version tracking for the future.
> > >
> >
> > Is the version tracking done during build time or runtime?
> > The question is: where will the code be increased?
>
> IIRC Goswin said that there are version checks at build time- However
> that will only affect consistency of the boot image and the cd image.
> The testing scripts should manage version consistency on the mirrors.
> However this might not be enough.
Apt-get is used to download and it uses a dpkg status file seeded with
the libs that will be pulled into the initrd from the main system (as a
workaround till they are shiped in udebs). Since apt-get does
dependenciy checks it will fail if a package becomes uninstallable. It
will download any extra depends bu they won't (yet) be unpacked or
copied to the images.
> Consider someone using a cd image which is a little older an then tries
> to use most recent udebs from unstable. This is presently possible and
> if we had version incompatibilities they would go unnoticed.
The versioned depends are most likely on libraries, of which only
reduced versions exist on the initrd. The newer full versions would be
pulled in. Versioned depends on busybox-cvs or cdebconf will be a
problem though.
MfG
Goswin
Reply to: