Re: [OctDev] main ported to the package system

[David B. <Dav...@mo...>]

S=C3=B8ren Hauberg wrote:

>
>I don't really know the first thing about CVS. What does .cvsignore do?
>And what should I do with them?
> =20
>
The .cvsignore file tells CVS the files that are created and so that
therefore can be ignore. CVS ignore *.o and *~ for example. With
.cvsignore we can make also ignore things like *.texi, etc. The basic
thing to do with them would be to copy them as is the src/ and inst/. We
can deal with cutting down their contents later.

> =20
>
>>The version numbers you added to fixed doesn't correspond to the
>>existing version number used internally in the code. Fixed should be
>>0.7.0...
>>   =20
>>
>Sorry :-)
>Since I didn't know anything about the internal version numbers, I've
>chosen that all packages are at version 1.0.0, which needs to be changed
>in the individual packages. Also, information about maintainers (etc.)
>needs to be corrected on a per package basis.
> =20
>

No problems... The maintainer, should be someone who will continue to
maintain the package, and not necessarily the original author. Not that
many people are active over the long term and so I wouldn't hesitate to
make the maintainer someone who isn't an author. However, the person
must agree to be the maintainer. I agree to be the maintainer of at
least comms and fixed. Maybe I'll agree to others later. We need
agreement from others to maintain the packages once the initial
development phase is complete. We can then identify orphaned packages.

Also with some of the directories it problem makes sense to convert them
to several packages. For example the xml stuff in miscellaneous should
probably be a seperate package.

> =20
>
>>> The file called octave-forge-main-<date>.tar.gz is a bundle of all th=
e
>>>packages, but it can't be installed without a patch to pkg that you ca=
n
>>>find on the octave-bug list.
>>>
>>> I can't install the packages called "parallel", "comm", "fixed", and
>>>"linear-algebra" due to a problem in ./configure. However, that proble=
m
>>>has been hunting me since before the move to the package system, so my
>>>problems shouldn't be related to the package system.
>>>=20
>>>
>>>     =20
>>>
>>I'll look at comm and fixed as these are my stuff.
>>   =20
>>
>My problems are related to the configure script, but once the #ifdef's
>go away, so will my problems.
> =20
>
Ok, then I'll work on removeing the ifdef's first..

>Okay, but this stuff can be handled on a per package basis, and we can
>easily make releases even though the #ifdef's, etc. haven't been removed
>(my point: we're not in a hurry).
> =20
>

Agreed...

Cheers
David



--=20
David Bateman                                Dav...@mo...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob)=20
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)=20

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary