incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: Draft IP Review Plan for OpenOffice
Date Thu, 17 Nov 2011 20:30:56 GMT
I had thought that category X artifacts needed to accomplish a build would be excluded from
the release but identified as prerequisites for the build.  They would never be distributed
in the Apache OpenOffice release.  (I am becoming rapidly accustomed to using that name.)

Some become downloaded by build procedures in order to be used, but they are never in the
release itself.  (Whether an ASF-hosted buildbot does such a thing is interesting but tangential,
I think.)

There are some odd cases of abandonware having no authoritative location for downloading and
also having patches.  I think dmake is one of those.  I have no idea
how that ends up but I think it means dmake disappears as a build prerequisite.  

Another case would be redistributables (e.g., a particular JRE version or Microsoft Visual
C++ redistributables) that may end up in a binary distribution.  This is a different situation,
even though there can also be build-time prerequisites (e.g., on a JDK or Visual C++) as well
as dependencies in the built binary distribution.

TJ, do you see any other flavors, or have any other specific cases in mind.

-----Original Message-----
From: TJ Frazier [] 
Sent: Thursday, November 17, 2011 11:44
Subject: Re: Draft IP Review Plan for OpenOffice

On 11/17/2011 14:16, Rob Weir wrote:
[ ... ]
> Regards,
> -Rob
Good job, and much needed.
(a) For item #4 under "Guidance for Source Releases", I suggest:

s/This/Producing a copy-left-free binary/

(b) Some further explanation of the situation regarding class-X-licensed 
build components would be helpful. In order to build, AFAIK, we need all 
sorts of things, like dmake, epm, gcc, &c. These have to be present or 
downloaded, true?

View raw message