[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
packaging system
From: |
Stefan van der Walt |
Subject: |
packaging system |
Date: |
Wed, 15 Jun 2005 20:44:36 +0200 |
User-agent: |
Mutt/1.5.6i |
On Wed, Jun 15, 2005 at 02:08:06PM -0400, John W. Eaton wrote:
> On a related topic, it would be useful to have a packaging system for
> contributed Octave code. That would allow people to independently
> distribute collections of functions. Octave forge would still be
> useful as a place for collaborative deveoplment, but we would not be
> restricted to a monolithic Octave plus a monolithic Octave forge
> collection. Given a functioning package system, there are a number of
> things that could be removed from Octave and placed in independent
> packages.
I suggest that we take a look at the Debian package format, and create
a similarly structured archive. This archive will, for example,
contain the following:
pre-install.m
post-install.m
pre-remove.m
post-install.m
content.tar
INDEX
Then, some choice functions could be provided to aid the pre- and
post-install/remove scripts. The INDEX format used in Octave Forge
works quite well -- and we already have a parser for it, written in
C++.
Regards
Stéfan
- packaging system,
Stefan van der Walt <=
- Re: packaging system, Quentin Spencer, 2005/06/15
- Re: packaging system, John W. Eaton, 2005/06/15
- Re: packaging system, Przemek Klosowski, 2005/06/17
- Re: packaging system, Søren Hauberg, 2005/06/17
- Re: packaging system, John W. Eaton, 2005/06/17
- Re: packaging system, Søren Hauberg, 2005/06/17
- Re: packaging system, Søren Hauberg, 2005/06/17
- Re: packaging system, Stefan van der Walt, 2005/06/18
- Re: packaging system, Søren Hauberg, 2005/06/18
- Re: packaging system, Stefan van der Walt, 2005/06/18