Re: SML/NJ Packaging Difficulties

2003-07-16 Thread Sven Luther
On Tue, Jul 15, 2003 at 08:04:07PM -0700, Aaron Matthew Read wrote: > The smlnj package (the compiler) is implemented in sml and needs a > working implementation to build. Upstream, a set of pre-compiled > binary files (~4 MB each) are supplied for each platform. > > When I initially supplied the

Re: SML/NJ Packaging Difficulties

2003-07-16 Thread Aaron Matthew Read
Matthew Danish points out that the cmucl package has itself as a build-depend. I would just have to supply a binary package that I compiled myself. It strikes me right away as being the correct solution. It would eliminate the need for binary images in the source package and doesn't require the c

Re: SML/NJ Packaging Difficulties

2003-07-16 Thread Sven Luther
On Tue, Jul 15, 2003 at 08:04:07PM -0700, Aaron Matthew Read wrote: > The smlnj package (the compiler) is implemented in sml and needs a > working implementation to build. Upstream, a set of pre-compiled > binary files (~4 MB each) are supplied for each platform. > > When I initially supplied the

Re: SML/NJ Packaging Difficulties

2003-07-16 Thread Aaron Matthew Read
Matthew Danish points out that the cmucl package has itself as a build-depend. I would just have to supply a binary package that I compiled myself. It strikes me right away as being the correct solution. It would eliminate the need for binary images in the source package and doesn't require the c

Re: SML/NJ Packaging Difficulties

2003-07-15 Thread Matthias Urlichs
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-)deb

SML/NJ Packaging Difficulties

2003-07-15 Thread Aaron Matthew Read
The smlnj package (the compiler) is implemented in sml and needs a working implementation to build. Upstream, a set of pre-compiled binary files (~4 MB each) are supplied for each platform. When I initially supplied the smlnj package, I shortsightedly only included the binary images required to bu

Re: SML/NJ Packaging Difficulties

2003-07-15 Thread Matthias Urlichs
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-)deb

SML/NJ Packaging Difficulties

2003-07-15 Thread Aaron Matthew Read
The smlnj package (the compiler) is implemented in sml and needs a working implementation to build. Upstream, a set of pre-compiled binary files (~4 MB each) are supplied for each platform. When I initially supplied the smlnj package, I shortsightedly only included the binary images required to bu