cvs commit: ports/editors/openoffice-1.1 Makefile

[Nakata Maho]

In Message-ID: <4055FE90.1020000 at fillmore-labs.com> 
Oliver Eikemeier <eikemeier at fillmore-labs.com> wrote:

Dear all,
thank you very much for many suggestion and discussion.

> No reason to get upset. I guess the suggestion to move development to an 
> private repository is `a positive spin', and should normally ease development 
> a lot, since you don't collide with other commits, have more freedom for 
> development and have a broader audience for testing. The cited projects 
> (gnome, kde) are not small either and pretty successful with this approach.

I also don't upset :)

I'm very glad if someone prepare some CVS repo for me.
I personally own sourceforge.jp administrator right esp. for upload space,
but many people around here might not understand Japanese, and re-getting
account for sf.jp is tedious.

There are IssueZilla (like bugzilla in other community) named meta-task
`FreeBSD-4.8: Meta task - build OOo'
http://qa.openoffice.org/issues/show_bug.cgi?id=18060
so anyone who are interested in porting OOo can participate.
Main discussion place is dev at porting.openoffice.org.

Anyway, at the moment, I think collide with other commits might not be
a serious problem for us.
Since submitting any patches requres Joint Copyright Assignment
(JCA) to SUN Microsystems. otherwise, patches won't be integrated for main tree,
or re-written by the person who signed jca.
Maybe only mbr and maho(me) is the person who have signed to JCA and also having
commit right to FreeBSD ports tree.

I don't think marked as IGNORE for 1 week is not the big problem for FreeBSD
community. If someone needs working port, he/she can easily pull down from CVS
repositry. Remember, mbr has been working for 1 or 2 years at openoffice-devel
under BROKEN and I have been submitting draft of working 1.1.1b,
1.1.1a(non working) several mailing list e.g., dev at porting.openoffice.org or
openoffice at FreeBSD.org.
Before starting my job, I stated ``I'll work on this'' at mailing list.

I think there are at least two possiblity: 

o development at port CVS repo is not a good way for FreeBSD community
  -> please get an account for public CVS repo for me

o repo copy should be done as openoffice-1.1-devel and
  merge final product to openoffice-1.1. development of OOo should
  be done for openoffice-1.1-devel.
  -> please do repocopy request

Sorry, I'm extremely busy,
if someone can help us, please contact us and do it.
Oliver, can you help us?

Any comments are appreciated.

thanks,
 nakata maho