On 28/10/10 04:14 PM, Juan Antonio Castro Garcia wrote:
The link you posted shoehorns one linux's packaging distribution
methodology into another packaging system. Best to keep them separate.
Don't mix RPM, YUM, Debs, et al. I would sooner install from source if a
deb were not available before I would even "consider" going the
methodology suggested on this page. Its not recommended to tell a newbie
to "do it this way" when it is inconsistent with the methodology for
installing software for her/his platform.
2010/10/28 Matteo Sisti Sette<firstname.lastname@example.org>
On 10/28/2010 06:01 PM, Frank Esposito wrote:
the link I posted had instructions for both. The link you referenced is
for a temorary repository, which works great too!
With the exception of Debian/Stable (which only changes because of
security upgrades), Debian has temporary repositories also
(testing/Squeeze, unstable/Sid, experimental). The only difference is
that Nikola's work isn't "approved" by Debian, but its packaged
expressly for Debian systems (i.e. going through the Debian build
I sense a lot of pain and learning for you. IMO, Ubuntu packages the OS
so it looks pretty. I'm not particularly fond of how Ubuntu adds stuff
to packages, but the Linux they produce is (for the most part) stable.
Its the extra stuff that they put as default into their version of the
Linux desktop that has kept me away. But, this is a learning experience
for you. If you haven't blown up an operating system lately, you haven't
been trying hard enough. :D
I usually expect any software I download to automatically install itself
with a click. Which is what usually happens when you use any "popular"
operating system (and distro in the case of gnu/linux).
I agree that a standard "README" file should be put into the package
with the instructions. Makes sense.
However, there is only so much detail that can be put into "install
instructions". IMHO, a guess was made that the average Linux user knows
how to install a package for her/his OS. However, this is part of the
joy of learning Linux, learning how to do something that works for you
and that you are comfortable doing (getting "positive feedback").
Thanks for the replies. I didn't mean to ask you how to install
LibreOffice. My point was that installation instructions should be included
with the package and/or in the download page.
Or much better, instead of telling the user what he should type in the
terminal, put it into a script and call it something like "setup".
(There is a link at the top of the page that will help direct you to the
Ubuntu wiki pages for your preferred language)
The Ubuntu wiki will be your best friend. It will help to "flatten the
learning curve". I would suggest that you bookmark the wiki home page.
It is stuffed full of very useful information especially useful to new
With this script you can install LibO into operating systems baseds in
To download .deb packages:
More help, in Spanish:
Making people go through the hassle of downloading from megauploads for
a one line script?
If you're going to call something an auto installer script make it do
something useful like:
- downloading the file
- extracting the contents
- doing the package install.
Not the most effective use of bandwidth.
E-mail to email@example.com for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/documentation/
All messages you send to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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