Hi, Aaron Matthew Read wrote:
> 3. For each platform, create a source package, for example: smlnj-x86
> which would contain the appropriate boot image. These packages
> would provide smlnj as a virtual package. Seems the best solution.
4. Package the upstream image files as a (somewhat-)debian-native
package named "smlnj-image".
Clearly state in the description that this package is used for building
smlnj only and isn't needed for normal use.
Build-Depend on it in your smlnj package.
Let the smlnj-image source contain files named smlnj-x86, smlnj-hppa
etc. Let debian/rules install the arch-specific image to
debian/tmp/usr/lib/smlnj/boot-image or so.
When building the "real" smlnj, you can now use
/usr/lib/smlnj/boot-image as the initial compiler image.
The advantage of this approach is that the "real" smlnj package isn't
cluttered with unpatchable binaries and that you only need to update the
unpatchable -image package when absolutely necessary.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
--
"The reasonable man adapts himself to the world; the unreasonable one persists
in trying to adapt the world to himself. Therefore all progress depends on
the unreasonable man."
-- George Bernard Shaw
