cvs commit: ports/editors/openoffice-1.1 Makefile

[Oliver Eikemeier]

Nakata Maho wrote:

[...]
> 
>>Wouldn't it be better to come up with a patch and port it for review,
>>than using the FreeBSD CVS for development?
> 
> No. currently I cannot do it. Since OOo is huge port, comparable to
> entire FreeBSD sourcecode. Maintaining this port is extremely difficult
> if there's no such kind of thing (e.g., patch without IssueZilla ticket),
> we are soon confused what are committed or what aren't.
> 
> My standpoint is reduce OOo patches to build as far as possible(remember,
> there were over 120 patches to build), however, 
> still we have many (minor or major) problems, so we have ~10 patches. 
> IMHO, development speed of OOo is extremely fast. to catch up with it, such kind
> of things are quite necessary.

How about a private CVS repository, like gnome, kde or many other projects
have? You leave FreeBSD useres without a working OpenOffice.org port, and
I can't really see the benefits of your approach.

Just my 0.02 €
    Oliver