Re: [OctDev] Using the package system

[Paul K. <pki...@co...>]

On Aug 7, 2006, at 1:34 PM, S=F8ren Hauberg wrote:

> s=F8n, 06 08 2006 kl. 07:27 -0400, skrev Paul Kienzle:
>> If you needed to change the package manager in order to make it work=20=

>> in
>> octave 2.9.7 then we will have to wait for the 2.9.8 release.
> Wait before we make an octave-forge release, or wait before we check
> changes into cvs?

If the current octave-forge works with 2.9.7 then you can start checking
in changes now.  Anybody tried it?

Otherwise wait for a new release.

>
>> The octave-forge build/release infrastructure will need to be changed
>> to make the packages available individually and as one large =
download.
> When you say one large download, do you mean a large package (to be=20
> used
> with the package manager) or a download that is installed in the=20
> regular
>   ./configure; make; make install
> way?

I mean some way to download and install a bundle of packages all at=20
once.
Presumably this would be a simple script that walks through every=20
package
in the tree and asked it to confirm its prerequisites, build, test, and
perhaps install while collecting a summary of the results to present to
the user when the process is complete.

>
>> A convenience installer allowing the user to select the list of=20
>> packages
>> to install would be nice.
> Agreed, but that's a not a problem that needs solving right now.
>
>> The extra and nonfree directories will need
>> to be packaged as well.
> This should be trivial (1-2 hours of work) and I'll do it soon.
>
>> Any volunteers?
> I'd love to help out, but I really don't know anything about =
autotools,
> and I have a feeling that such skills will be needed.

There shouldn't be any global autotools.  It should only be a matter of
asking each package to detect whether it's dependencies are met.  This
is currently encoded in the configure.add file.  There are some global
checks done in the top level configure which hopefully are no longer
needed.

- Paul=