SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm not certain if adding an 'if' statement there instead is overkill?
I doubt adding 1 more would be overkill, even there. But if you ask me, i do think you could section the code into functions... It'll make debuggin, upgrading, easier, and reduce the code.
Also, it's a bit irritating downloading 10 files... Could there be a possibility that you can stick all the text files into the bottom of the script, which will be called in the beginning, creating them with something like
Code:
base = <the text>
calc = <the text>
...
for loop
cat base >> EOF
$base
EOF
or to make it even more insane.. a matrix array[][]
Its insane, but fun.. i admit
Minor update to the SlackBuild script (s/mandrake/mandr/ - to account for the renaming of mandrake to mandriva, but maintain backwards compatibility).
http://slackbuild.strangeworlds.co.uk/ooo (If you have the 1.9.100 version, you only need to update ooo.SlackBuild. Otherwise, download all files and read the top of ooo.SlackBuild if you're not sure what to do. The tar.gz is just an empty file - you need to get the real one of the same name from OOo).
Reasons to be cheerful?
1) OOo load up time has improved greatly.
2) Probably some bug fixes
3) Need for speed - See 1!
Then I uploaded the empty file created (with shell access, you could just run the command directly on the server) - it doesn't do much, but does provide a useful placeholder to the file I expect to be there.
I updated the original post (see beginning of thread) to reflect the simplied installation for current snapshots of OO2. I've been installing and testing most of the previews since 1.9.65, and the process has gotten more straightforward since then (I'm now at 1.9.120.)
Xushi's script (see above) makes OO2 installation even easier.
Whilst Xushi contributes, provides CVS, kick in backside where needed, etc, I'm the maintainer of the ooo.SlackBuild you're referring to.
Also, where is 1.9.120 available? The latest release I can find is 1.9.118.
ooo.SlackBuild users:
Sorry about not getting a 113 SlackBuild out on time, but I was on holiday when it came out. And since 118 is now out, I've fixed the script for that instead (the extra directory from 113 has now been dropped, though a slight renaming of the input file has occurred). It should also be slightly more space efficient in converting the RPMs to TGZs (i.e. it will now convert then delete each RPM individually, rather than convert all of them and then delete them).
(Bonus Points: From 113, user information is now saved to ~/.openoffice.org2 instead of a build specific directory in ~. This means you will no longer need to keep reimporting settings/moving directories, etc between builds.)
Oops. Very sorry, cathetic. I misread one of xushi's recent posts and got the idea that he was maintaining the excellent OO build script. I knew that you had originated it and I should have double-checked before posting.
I found m120 here, though note that it might be a custom build (and hence might pose probs for your script):
Since I believe your script is version specific (yes?), and since these early builds don't seem to be available on most mirrors, you may not even want to tailor your script for these builds (though I'm sure some eager beavers out there would be very happy if you did).
These people nearly always have a later snapshot than the official OO.org site. I don't know exactly what that means; maybe you do.
I can say that haven't seen any differences in the stability of the ftp.linux.cz OO builds and the official ones, and I've been using the English OO packages from here for a good while now (maybe six weeks).
I hope posting this link doesn't overtax their server(s).
The LinuxPackages package is an old build, and they don't keep up with the releases of the latest builds. Hence the SlackBuilds so we can roll our own packages quickly.
For OOo language pack users, I've put together a SlackBuild (based on some earlier work I did in another thread somewhere) that will get the language packages out of the shell-script-&-tar.gz-rolled-into-one-monstrosity that OOo provide, and convert them into nice-ish Slackware packages (no slack-desc's with the files yet though).
1) Download ooo-langpack.SlackBuild
2) Put your language pack file in the same directory
3) Edit ooo-langpack.SlackBuild, and ensure the 'LANGUAGE' variable is correct ('es' for Spanish (Spain), 'pt-BR' for Portugeuse (Brazilian), etc).
4) Run as root/ using su.
I've tested it with the Spanish packages, and it appears to work fine. You should be left with three files in /tmp
openofficeorg-${LANGUAGE}-1.9.118-i586-1.tgz - Translations for wizards, some images, and dictionaries
openofficeorg-${LANGUAGE}-help-1.9.118-i586-1.tgz - Exactly what it says on the tin, I think. Translated help files?
openofficeorg-${LANGUAGE}-res-1.9.118-i586-1.tgz - Don't know. More translated stuff?
Install them all with 'installpkg'. To change language, load up an OOo 2 program (e.g. Writer), then Tools --> Options --> Language Settings --> Languages. Adjust 'User Inteface' as necessary, click 'Ok' then restart OOo. Same procedure to return OOo to English, just select 'English USA' (no en_GB yet...).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.