Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


I didn't say I didn't know how to do it.  I didn't say I wanted to build it.  This is about 
honoring the spirit of the free software promise.  It is not even about building the code.  People 
may want to do any number of things with the source code (inspect for bugs, for example).

I *did* say I don't see where the distro tells me how to find it and I don't see where the download 
page lets me find it "in the same way" (and now I can't even find the version that I am running). 
20-21 tar.bz's are also rather intimidating, but way better than nothing.

So, where is the link on the web site that would let me find the version I am running and the 
source code for it?  (The same question for dependency derivatives is a bonus question.)

 - Dennis

-----Original Message-----
From: Simos Xenitellis [mailto:simos.lists@googlemail.com] 
Sent: Friday, June 17, 2011 16:31
To: discuss@documentfoundation.org
Subject: Availability of source code (Was: Re: OFF TOPIC about GPL enforcement (Was: Re: 
[tdf-discuss] Re: [Libreoffice] Proposal to join Apache OpenOffice))

On Sat, Jun 18, 2011 at 1:30 AM, Dennis E. Hamilton
<dennis.hamilton@acm.org> wrote:
[ ... ]
I have a copy of LibreOffice 3.3.2 installed on my computer.  I am looking for any place that I 
am offered access to the specific (or, indeed, any) source code for the LibreOffice 3.3.2 
distribution that I have installed (en-win-x86).


Admittedly, I never checked the UI text as to where you can get the
source code.

To build LibreOffice, I would simply follow the instructions at
http://wiki.documentfoundation.org/Development/How_to_build
which cover different operating systems.

[ ... ]

Your question is actually about whether we can make the Help→License
information more informative
so that users who would like to build LibreOffice, will get directed
to the How_to_build page.

[ ... ]

If I follow the "Download the source code to build your own installer" (why does that have to be 
the reason?), I see a set of logs that tell me nothing.  Under 3.4.1.1, 3.4.0.2, and 3.3.3.1 I 
see lists of 20-21 tar.bz2's.

Well, maybe that qualifies.  Maybe not.  But what about for my 3.3.2?


Indeed, the 3.3.2 version is not showing, because there are newer
versions (3.4.1, 3.4.0 and 3.3.3) and the 3.3.2 does not fit to be in
that page.
You can get 3.3.2 files at
http://download.documentfoundation.org/libreoffice/
http://download.documentfoundation.org/libreoffice/old/src/

As I said earlier, if you really want to compile, you would go for the
'git repositories' and the instructions at
http://wiki.documentfoundation.org/Development/How_to_build

AND ABOUT THOSE DEPENDENCIES

If any of the listed dependencies also have derivatives used, is there some place where, ahem, 
those modified sources are available in some suitable way?


See the dependencies at
http://wiki.documentfoundation.org/Development/How_to_build#Dependencies

Simos

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted


-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.