[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Peter Novodvorsky <nidd@debian.org>] Re: [dev] Re: Some Issues regarding Debian versus OOo versions and Support?



--- Begin Message ---
Hi, Kevin!

"Kevin B.Hendricks" <kevin.hendricks@sympatico.ca> writes:

> Hi,
>
>> >1. Why are you disabling the mozilla addressbook builds.  They are easy
>> > to do just by building mozilla-0.9.5 and making some zip archives.  I
>> > once explained the steps to do this and I could propbably find them in
>> > the OOo mailing list if need be.
>>
>> I remember that, but I cant find the mail :(
>> Copiing the mozilla-0.9.5 files into oo_src is a change of orig.tar.gz,
>> which is the original source from upstream .. from you! :)
>> If we copy the files into it, to build OOo on PPC with mozilla, we will
>> break with our policy .....
>>
>> As workaround, I commented it out for PPC build, to create a debian-
>> package first. Then we can work on a fix :)
>
> I think we can actually change the makefile.mk to build right from the 
> Mozilla 0.9.5 build tree.  So would it be a problem with your policies to 
> have both trees being used for the OOo build at the same time.  Not 
> patches are needed for Mozilla as long as you use mozilla 0.9.5.
>
>> gpc is not removed at all.
>> Peter Novodvorski created a replacement, so we can drop gpc. He
>> announced it, here:
>>
>> 	http://lists.debian.org/debian-openoffice/2002/debian-openoffice-200204
>>/msg00069.html
>>
>> but it does not work yet. 
>
> That's great!  But Peter has never mentioned that on dev@openoffice.org 
> has he?  I did not see any announcement.  How close it it to
> working?  

It's not as great as it seems :( It's true that I've made some
prototype of replacement, for gpc, based on multclip. But I found that
it doesn't support many features and it's algorithm goes in infinte
cycles while working with self-intersecting polygons. 

Currently I have working stub for gpc. The only problem it creates:
when you are printing polygons with gradient background, it won't
print background and leave it blank. 

My company is thinking about possibility of giving money to one of
labs in our univ (graphics labs, graphics.cs.msu.su), so it'll create
library comparable to gpc. But things are unclear now. It may cost
~2000$. 

>
>> >3.  Why remove java from the build?  Is this again a license issue. 
>> > You are allowed to ship Sun/Blackdown jres along with OOo.  There are
>> > Blackdown Debian java packages that can be used for the build itself.
>> > Will you allow Java's use or are you disabling it in the setup
>> > process?
>>
>> First, using Java for building OpenOffice.org will cause, that
>> OpenOffice.org will come into debian/contrib, or in worst case,
>> debian/nonfree. In this case, OpenOffice.org do not get the full support
>> by debian, eg. autobuilders etc etc ....
>>
>> Java is highlly nonfree software, and we do not want to build
>> OpenOffice.org with Java sometimes in the future!
>> I expect OpenOffice.org in main, this means, that we find a replacement
>> for gpc and try to use gcj as replacement for Java. I will recommend
>> that.
>>
>> For further informations, please have a look at:
>>
>> 	http://www.debian.org/social_contract#guidelines
>> 	http://people.debian.org/~opal/java/policy.html
>>
>> And yes, we disabled java in the setup prozess.
>
> But what if we supply the needed classes code (built with jikes) to 
> interface to Blackdown's Java (already Debian packaged) and leave it in 
> the setup process.  If Java is not found, no harm done.  If java is found 
> (the user has already installed the Blackdown Java jre or jdk, then you 
> could recognize it and use it as normal.

It is debian idealogy. I ask you again to read DFSG (debian free
software guidelines). If package depends on non-free software (no
matter, if it is freely distributable, it is NON-FREE. dixi.) it's not
100% pure, and we don't like it as much, as we like software from
main. 

Another thing is debian autobuilders. If package is in non-free or
contrib, it won't be autobuilt.

> If you join OOo then go ahead and tell Debian users to use Issuezilla 
> because you will be there to help run the test cases and things and let me 
> know where the code differs at all.  Then I am very happy.  No need to 
> redirect things to debian-openoffice unless you want  to.

I'd like users to post bugs to Debian BTS and openoffice specific bugs
(not package ones) will be forwarded to IZ. 




--
Nidd.

--- End Message ---

-- 
--
Nidd.

Reply to: