Re: Future development
Ken Foskey wrote:
> >Have you considered running a semi-public development CVS Repository
> >for the OpenOffice source already? You could request /cvs/openoffice
> >on cvs.debian.org and move the current source into it.
> >
> Why have two source repositories. This seems a little risky. If you
> can package getting the correct support libraries and doing the current
> cvs get command so that there are fewer people trying to get head from
> oo.org. The package could be updated when official releases are
> anounced and verified.
One a release has been converted into a bunch of Debian packages
further development is much easier. However, getting this first step
done seems to be quite painful.
> >This way, more people can use the current code with all current
> >patches in order to improve the system and be able to build packages
> >earlier. The repository could be accessed though cvs/pserver so more
> >people can get involved.
> >
> I am concerned with the patches on the external components. The
> community needs to validate and apply them to the appropriate upstream
> libraries. We can then work on splitting out the external stuff out
> from core OO source.
>From what I heard, there will be a lot of patches to get the build
system running, to get autoconf work, to get support for the proper
libraries working, maybe also to get modularization running etc. It
was my impression that upstream didn't like these patches, so they'll
have to be stored somewhere.
>From my point of view it seems that there are a couple of people
working on debianization, but have their source files on their private
machines, while it is more work than these individuals can do, which
lead me into thinking that an open repository could help.
> >For packaging, I'd suggest using DBS and not the native Debian
> >packaging system. This way you'd benefit from collecting small
> >patches instead of building one huge patch against the native package
> >out of it. One problem though, documentation is not easy to
> >find... For an example, see Apache or XFree86 packages.
> >
> What patches are you intending? I am a recent convert and not done
> open development so forgive my ignorance.
See above.
> >I'm little concerned about the progress of this package...
> >
> It is only now that I would consider creating a package. When I first
> started the build was just about impossible, now I might even be able to
> work on it instead of just struggling with it.
So work on the same source like Jan-Hendrick and Bernhard.
Regards,
Joey
--
In the beginning was the word, and the word was content-type: text/plain
Reply to: