Re: Slink CDs - boot floopy images?
Steve McIntyre wrote:
> >> >This won't work. Simply due to slink/main is 750 MB big and the CD
> >> >can only contain 650 of them. Thus the Packages file cannot reflect
> >> >the contents of the cd archive.
> >> Agreed in that the normal Packages files will list more than just the
> >> contents of each CD, but I'm thinking of putting them on anyway as maybe
> >> another check...
> >This is not quite useful since you won't be able to use them. If they
> >would reflect the current archive you could still access them with regular
> >mount methods for dselect.
> Suggestions, then? I could simply sym-link Packages.cd to Packages in each
> case, assuming the standard mount methods won't be thrown by the extra
> X-Medium field...
Jason Gunthorpe asked for regular Packages files in common places
and Packages.cd only additionally. This means per CD you have to
manually create a set of Packages and Packages.cd files. (You could
modify dpkg-scanpackages to produce both in one run though.
Linking Packages and Packages.cd together is not useful since
main/binary-$arch/Packages.cd contains all files in the main
distribution, on *all* cds. In that case you'd end up with the
same problem that started this discussion. :)
A mathematician is a machine for converting coffee into theorems.