I remember seeing an install direction for a Linux package that has the
"generic" information instead of the current numbering system. It
worked well enough. YET, for some users, you might need to state . . . .
"LibO_#.#.#_Linux_x86_install-rpm_en-US"
replace the current version number for the "#.#.#",
example
LibO_3.6.5_Linux_x86_install-rpm_en-US
On 11/16/2012 07:21 AM, Marc Paré wrote:
On the Linux installation webpage[1], there are mentions of
LibreOffice by specific release numbers. I propose we make the
instructions as release generic as possible.
If we do this, it will mean no more updating the webpage after each
new release. In the case of this page, it has not seen an update since
the release of version 3.4! Worse, there are many file names in the
text that need updating. It would be better if we made the file names
generic and not release specific.
Here are some examples of changes that I propose.
=======================
On the Linux installation page, the following sentence is found:
"Instructions below apply to all final releases of 3.3 and 3.4"
I don't think we need this sentence and I would like to delete it.
IMO, our instructions for installs should avoid mentioning LibreOffice
versions unless absolutely necessary.
I've checked the .rpm procedures and they are the same procedures a
user may use for any version we have released.
=======================
In the .rpm section, the instructions also mention the folder name by
version. I would like to make these names more generic. For example:
Original:
"1) After downloading the installer archive file, use Nautilus to
decompress it in a directory of your choice (your Desktop directory,
for example). After decompressing it, you will see that the contents
have been unpacked into a directory called
LibO_3.3.0rc1_Linux_x86_install-rpm_en-US or
LibO_3.4.5rc2_Linux_x86_install-rpm_en-US. Open a Nautilus file
manager window, and change directory to that directory. ..."
Change:
"1) After downloading the installer archive file, use Nautilus to
decompress it in a directory of your choice (your Desktop directory,
for example). After decompressing it, you will see that the contents
have been unpacked into a directory called
"LibO_X.X.X_Linux_x86_install-rpm_en-US". Open a Nautilus file manager
window, and change directory to that directory. ..."
=======================
Note: I find the Linux Installation page extremely hard to follow. I
would propose that we re-organize the page so that once a Linux user
lands on that page that she/he be greeted with a link the following
sub-pages:
* Installation of LibreOffice on Debian/Ubuntu-based Linux systems
* Installation of LibreOffice on Fedora, Suse, Mandriva and other
Linux systems using RPM packages
Any remaining information would be moved and/copied into either
section as needed.
The user will then be presented with less information rather than
having to deal with a lot of text. We need to reduce the amount of
un-needed text.
=======================
If we all agree to the above, I would be willing to go ahead with the
changes. We would have to have someone check with the .deb install
procedures to make sure they have not changed since the last page
update. The .rpm install procedures look OK to me.
Cheers,
Marc
[1] https://www.libreoffice.org/get-help/installation/linux/
--
Unsubscribe instructions: E-mail to marketing+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/marketing/
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.