[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Reviewing data in the debian-cd packages

Daniel's helpful bug (#497270) points out that we have embedded copies
of isolinux in the debian-cd package. It's prompted me to look for
other embedded data, and I've found the following list:

tack:~/debian/debian-cd/debian-cd$ find . -type f | xargs file | \
    grep -v text | grep -v -e \.png -e \.jpg -e \.gif | \
    awk '{print $1}'

Of those:

 * isolinux.bin and vesamenu.c32 come from the syslinux package
 * sbm.bin.gz comes from the sbm package

I can add code to extract the appropriate binaries from each package
at CD build time, in much the same way as we use debootstrap from the
archive. It'll slow things down a little, but that's not as important
as following licensing.

There's another implication, though... Normal weekly builds will
automatically pick up the appropriate source as part of the source
CD/DVD builds, so they're OK. However, more painfully, the current
daily netinst/businesscard builds don't produce source images. If
things change quickly in the syslinux/sbm packages there is a chance
that the source for the exact versions used in the daily images may
not remain on the mirrors. To be totally safe, we'll need to track
versions of packages that go into the daily images (both packages and
the used binary files) and archive those too. "Yay".

Other files (hence the cc: to the m68k folks):

 * cts_amiga_info.tar.gz
 * macinstall-cd.tar.gz

are both provided to boot m68k machines, and they each contain binary
files (icons and boot files, AFAICS). I have no idea how those files
are generated, nor what the licensing situation is for them. Can you
help out please?

Steve McIntyre, Cambridge, UK.                                steve@einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver." -- Daniel Pead

Reply to: