Re: [OctDev] Using the package system

[Quentin S. <qsp...@ie...>]

S=C3=B8ren Hauberg wrote:

>Hi,
>
>tir, 08 08 2006 kl. 08:35 -0500, skrev Quentin Spencer:
> =20
>
>>Paul Kienzle wrote:
>>   =20
>>
>>>If the current octave-forge works with 2.9.7 then you can start checki=
ng
>>>in changes now.  Anybody tried it?  =20
>>>     =20
>>>
>>Yes, I have released the current octave-forge in Fedora Extras with=20
>>octave 2.9.7. The only problem so far is a small bug in legend.m, which=
=20
>>I have fixed in CVS.
>>   =20
>>
>So, I can start making changes in CVS? I need to be sure everybody is
>fine with this because I need to make some minor changes in the
>file/directory layout, that will break the build system.
>
>The package system assumes that
>* Files that can be directly installed (e.g. *.m files) are in a package
>subdirectory called 'inst'.
>* Files that need to be compiled are in a package subdirectory called
>'src'.
>
>So are everybody okay with me moving files around? If yes, then things
>will be broken for a while...
> =20
>

It's generally fine with me as long as the last release of octave-forge=20
still compiles with current 2.9.x octave versions. If there is a new=20
octave release that requires significant changes in octave-forge I will=20
want to see an octave-forge release. However, I think that's not so=20
likely since 2.9.x seems to be stabilizing a bit more now. So, unless=20
others object, I'd say go ahead and break things as long as they don't=20
stay broken for too long.

Quentin