On Wed, 11 Apr 2001, Raphael Hertzog wrote:
> > 2a) Check that the md5sums of the Packages-signed.gz and
> > Sources-signed.gz files you have match the md5sums listed
> > in the Release file
> > 2b) Check that every package listed in each Packages.gz and
> > Sources.gz exactly matches the corresponding entry in
> > Package-signed.gz or Sources-signed.gz, and that there *is*
> > a corresponding entry
> >
> > which is a fair bit more awkward.
>
> If you have to modify apt-cdrom at least you can make it manage this
> precise case. Use "Packages" file for knowing which packages are available
Why? apt-cdrom already stats every file to make sure it is available, I
have no desire or need to use a paired down file. All apt-cdroms will work
with what aj is proposing, but you will get a warning that a lot of files
are missing and that may mean the CD is bad.
I think the best suggestion was to have a Packages.cd which could be used
by non-apt tools that can't cope with extra file names (which are
basically random folks's personal scripts). I don't want to remane the
files referenced by the release file, that just gets ugly fast.
> I don't want to change the "standard" Packages files since those are used
> by all the old tools we have (including those that won't understand why
There are no old tools that reliably speak to cds and rely on Packages.
Jason
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
