Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <1338344515.60530.YahooMailClassic@web113503.mail.gq1.yahoo.com>
Date: Tue, 29 May 2012 19:21:55 -0700 (PDT)
From: Pedro Giffuni <pfg@apache.org>
Reply-To: pfg@apache.org
Subject: Re: [PROPOSAL] Starting the graduation process
To: ooo-dev@incubator.apache.org, sebb <sebbaz@gmail.com>
In-Reply-To: 
 <CAOGo0VY=i9K_p3nNdo_hTgvx=bd_+VjXv55M9iS2YHJtXspZEQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi;=0A=0A--- Mar 29/5/12, sebb <sebbaz@gmail.com> ha scritto:=0A=0A...=0A> =
>=0A> > This is admittedly a stop gap solution to comply=0A> > better with =
the Apache policies, the real fix would=0A> > be to work collectively on re=
placing the code that=0A> > can be replaced:=0A> =0A> Alternatively, it is =
possible to include cat B [1]=0A> dependencies in binary form.=0A=0AWe do t=
his for FreeBSD and it works great.=0A=0A> Is there any need to include the=
 source?=0A>=0ANo. The real reason why OOo historically has carried=0Athe s=
ources for everything is/was that previously the=0AGPL forced developers to=
 make the sources available.=0A=0AThe issue is the multiplatform support. F=
or builders=0Aon platforms like Windows it's not really fun to go=0Alooking=
 for the different dependencies. This said,=0Afor Java stuff it is perfectl=
y OK to include only=0Abinaries (except for our old saxon-B, which is=0Adep=
recated upstream so we have to carry the sources=0Asomewhere)=0A=0A=0A> [1]=
 http://www.apache.org/legal/resolved.html#category-b=0A> =0AWhile [1] is t=
he official document, I find the original=0Adraft policy explains things mu=
ch better:=0A=0Ahttp://www.apache.org/legal/3party.html=0A=0Acheers,=0A=0AP=
edro.