Hi :)
I think there is some confusion here.
Compile means something specific in OpenSource and is not the same as "get together" or "acquire".
Compile means taking the raw source code and installing that onto your system. It's nice to watch
the newly made youTube video to help with that but this whole process is waaaay more than most
people will ever need to do.
It's much easier to get the Debian-family installer from
http://www.libreoffice.org/download/
and then these instructions to unzip/unpack it and then install it.
http://wiki.documentfoundation.org/Installing_LibreOffice_on_Linux
If you want to create your own installer from the source code then i think that's called something
like, doing your own "build" and hopefully this link might help
http://wiki.documentfoundation.org/Development/Native_Build
Again this is waaaay more than most people will ever need. Mostly these days LO is installed by
default on most fresh new Gnu&Linux systems or grab it from the repos using the package manager.
Gnu&Linux distro fall neatly into about 6-8 different families. Many of the newer ones are in the
Debian family including ones such as Mint, Ubuntu. There's also a Redhat family, Slackware family.
Even different families often use the same installers so there are only about 4 different
installers needed to cover all the different distros.
You really don't need to create a differrent installer for each different release of each different
distro. That's the kind of craziness that hardware manufacturers seem to think in their ignorance
= or at least the excuse that often gets used by people who should know better.
As i understand it the main advantage of compiling the code from scratch is that it streamlines
your version of LO and tailors it to your specific set of hardware. So it should run faster and is
just more cool when you mention it to your mates. Unless you compiled your own version of Ubuntu
then you really don't need to go this route. Ubuntu is not really designed to be compiled from
scratch. It's meant to be an easy install where everything magically works without havign to do
much. There are other distros that are much better for this sort of thing, such as Arch, Tiny
Core, Slackware and they have loads of help geared towards helping people compile pretty much
anything they want.
Regards from
Tom :)
________________________________
From: Aaron C Johnson <acjohnson@pcdomain.com>
To: users@global.libreoffice.org
Sent: Thursday, 6 December 2012, 3:25
Subject: Re: [libreoffice-users] Ubuntu Libreoffice
Hello-
Are you simply trying to install the latest release of LibreOffice or
are you just interested in compiling it?
dpkg is the debian package manager so no that command doesn't extract
it, it installs the binary to your system.
There really is no need to compile it if you are planning on using it
for normal every day use.
If you really want to compile then I would suggest you watch this video
that was just created for this purpose:
http://www.youtube.com/watch?v=2gIqOOajdYQ&hd=1
:)
On 12/05/2012 09:08 PM, Anthony Easthope wrote:
Thanks! I'm guess that the "SUDO DPKG" command is meaning to extract the
files? i keep thinking there was something about a autogen.sh script (I
was reading about this somewhere on a compiling tuitorial) Doesn't LO
have such a thing?
On Thu, 6 Dec 2012, at 04:00 AM, Don Myers wrote:
Hi Anthony,
This is how I update to each new version of the Document Foundation
version of Libre Office. This is for the 64 bit version, but simply
substitute the 32 bit version for the 64 bit. This is for the latest
3.6.4.3 release:
Download LibO_3.6.4.3_Linux_x86-64_install-deb_en-US.tar.gz to the
desktop.
Right click on it and extract it to the desktop. This will give you the
folder LibO_3.6.4.3_Linux_x86-64_install-deb_en-US
Run the following terminal commands to install it:
1. sudo apt-get remove libreoffice*.*
2. sudo dpkg -i
~/Desktop/LibO_3.6.4.3_Linux_x86-64_install-deb_en-US/DEBS/*.deb
3. sudo dpkg -i
~/Desktop/LibO_3.6.4.3_Linux_x86-64_install-deb_en-US/DEBS/desktop-integration/libreoffice3.6-debian-menus_3.6.4-3_all.deb
I hope this helps you. This isn't exactly what you asked, but it does
work well for installing LibreOffice.
Don
On 12/05/2012 08:25 PM, Anthony Easthope wrote:
Hey guys
I'm back after what seems like ages! anyway encountered a problem which
is probably due to inexperience but anyhow.
I was wondering if there was a simple way to compile a Tar ball version
of LO on ubuntu? I've searched all documentation but its doing my head
in!
Cheers
--
Anthony Easthope
antisocky@myopera.com
--
**
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
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.