Re: [tdf-discuss] Problems installing LibO beta2 on Debian

On 16/10/10 20:20, Marc Paré wrote:
> Le 2010-10-16 13:00, AG a écrit :
> > On 16/10/10 17:37, Kertesz Laszlo wrote:
>
> > On a general note, I wonder if it would be worthwhile for the packagers
> > of LibO to (a) include installation instruction documentation somewhere
> > on their site where these can be easil;y found and used, and (b) to
> > develop a script that will actually perform the installation. While I
> > may not be the sharpest crayon in the pack, I obviously have had a fair
> > bit of problems installing this onto my machine and to be honest going
> > through this degree of hassle may well put some people off from even
> > trying it in the first place.
> >
> > Once again, Kertesz, my gratitude for your help and patience.
> >
> > Best wishes
> >
> > AG
>
> On the same note, I have also written up a detailed installation text 
> file for .rpm installation that could also be used in an 
> ReadmeRPM_KDE.txt file. This could be adapted and made a little more 
> generic. Here it is below.
>
> =================
>
> Just wanted to make note of the following. If you plan on installing 
> the LibreOffice v. 3.3 beta on linux, here are some steps that could 
> help you do an easier install if you are not used to using too much of 
> the console and prompt.
>
> Install process:
>
> Intallation (based on a KDE desktop Mandriva 2010.1)
>
> ===========
>
> BEFORE STARTING, UNINSTALL ALL PREVIOUS VERSIONS OF LIBREOFFICE WITH 
> THROUGH THE MCC AND THEN QUIT THE MCC
>
> 1. download LibreOffice from http://www.documentfoundation.org to your 
> "downloads" folder into a folder called "LibreOffice"
> 2. open Dolphin
> 3. browse to the "LibreOffice" folder in the "downloads" folder
> 4. right-click on the LibreOffice file and choose extract archive here
> 5. once extracted double-click on folder "en-Us" and then "RPMS" and 
> then "desktop-integration"
> 6. in Dolphin do F3 (this will split screen your window)
> 7. click in the right window once and click on the "UP" arrow in the 
> main menu bar up-above in Dolphin
> 8. you will now have the left window "desktop-integration" and right 
> "RPMS" windows open
> 9. in the left window drag the 
> libreoffice3.3-mandriva-menus-3.3-XXXX.noarch.rpm file to the RPMS 
> window and choose "Copy" **
> 10. in Dolphin do F3 and use the "UP" arrow till you are back at the 
> level where you see the "licenses", "readme", "RPMS" folders
> 11. right-click on folder RPMS and choose Action-Open Konsole
> 12. Konsole will now open with a $
> 13. in Konsole do $su  (this is super user mode)
> 14. type in your root password
> 15. in Konsole do #rpm -Uvih *rpm
> 16. wait till all the packages have installed
>
> -- ** for step 9. -- Note that if you are on Freedesktop drag the 
> corresponding file instead; if you are on RedHat drag the 
> corresponding file instead; if you are on Suse drag corresponding file 
> instead
>
> You will now have the LibreOffice v. 3.3.0 BetaX installed and in your 
> Mandriva menu. However, IF your KDE LibO menu items do not work. To 
> setup your Mandriva menu, right click on the "Mandriva" start button 
> (taskbar button with the star) and choose "Edit Menu". Find the 
> LibreOffice icon (in Office) and click on it once; the right-hand 
> window of the editing window will become active and choose "Command" 
> -- click on the folder icon and browse to the Opt/libreoffice3 etc. 
> till you find the right corresponding command file. Do the same for 
> all of the other sets of the LibreOffice icons in the start menu.
>
> Hope this helps those who wish to try the LibreOffice v.3.3. beta. 
> Remember, that this is a beta and may have some hiccups along the way. 
> The look and feel of the suite has still not been polished.
>
> =================
>
> Cheers
>
> Marc


Marc

These seem pretty comprehensive and detailed.  Nicely done!

Tangentially, this issue gives me conflicting opinions: on one hand, and 
harking back to my Slackware 8.1 days the installation of software was 
inevitably a manual effort on GNU/Linux  and one resolved the dependency 
hell as best as one could, following detailed instructions amended for 
one's own architecture and build.

The other part of me, now spoiled with apt and the point-n-click world 
reckons that these kinds of details should be passed upstream to 
developers to take care of.  The use of software has become such a 
mainstream activity that the standards of expectation are, IMO, higher 
than they were back in the late 1990s/ early 2000s when one was expected 
to RTFM and to bone up on countless man pages.

The former option may well breed more astute and reliable users and 
maintainers, but the latter is more likely to garner popularity.  If the 
objective is solid geek code (such as Theo de Raadt's OBSD), there is 
obviously nothing wrong about that but that is not likely to generate 
the user base for the world at large (which probably suits OBSD 
developers and users just fine).  It comes down to what the objectives are.

Assuming that LibO is going for a broader take up and diverse user base 
who want to use the software as a tool rather than as a project in 
itself, then it would make sense for this kind of thing to be passed 
upstream so that notes such as your own do not need to be so detailed 
and (relatively) technical.

In the meantime, if I used Mandriva I would find those very useful notes.

AG

PS (& OT):  I haven't touched Mandriva since it was Mandrake.  It was 
pretty cool, but Red Hat 7.2 was my starter and I found it such a joy to 
use at the time coming from MS Millennium and 98SE.

--
E-mail to discuss+help@documentfoundation.org for instructions on how to unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
All messages you send to this list will be publicly archived and cannot be deleted