Re: Executable packages (long, sorry)

2000-09-22 Thread Pedro F. Giffuni
Hmm... While I will not be contributing to this project, I wanted to remember everyone that the source code for UnixWare's packaging utility is available in Skunkware. FWIW, he Unixware stuff is very similar to Jordan's packaging utilities, in fact it has the same limitations. One thing I did l

Re: Executable packages (long, sorry)

2000-09-22 Thread Kris Kennaway
On Thu, 21 Sep 2000, Christian Kuhtz wrote: > Seems one might just as well investigate the SUN pkgadd format and see whether > such mechanism fits the bill... > > Ideally, the pkg also kows how to back itself out if it can't successfully > install. (although doing so should be an option, not th

Re: Executable packages (long, sorry)

2000-09-21 Thread Christian Kuhtz
Seems one might just as well investigate the SUN pkgadd format and see whether such mechanism fits the bill... Ideally, the pkg also kows how to back itself out if it can't successfully install. (although doing so should be an option, not the default). On Wed, Sep 20, 2000 at 06:49:36PM +0100,

Re: Executable packages (long, sorry)

2000-09-20 Thread Kris Kennaway
On Wed, 20 Sep 2000, Koster, K.J. wrote: > Riding on the wave of the unified BSD packages effort, this might be a good > time to rekindle that idea. Say that we agree on some form of uniform > package layout. You'd say that man pages go into $PKG_BASE/$PKG_NAME/man, > and that libraries go into $

Executable packages (long, sorry)

2000-09-20 Thread Koster, K.J.
Dear All, While we're on the subject of packaging formats, I would like to present an idea that has been running around in the back of my head. Years ago I had the pleasure of playing with a new RiscPC by Acorn. If you create a directory on RiscOS and stick a little BASIC script in with exactly