[SOLVED] AlienBob's LibreOffice 7.2.0 fails to start in Slackware Current after all updates
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.
[/CODE]
i show what LibreOffice.org can get direct all dependencies, and build automatically.
./configure
make
make install
Completed my experiment. First road block (I new this would happen), I needed to add "--without-java" to configure.
make went well.
I did not run make install though I ran:
make DESTDIR=/home/non-slack/slackbuilds/libreoffice/build/package-libreoffice/ install
I have not testing it yet, gonna login as a different user.
I don't like what it produces. I don't like using /usr/local/lib as the install directory. I made a package out of the result, it is three times bigger than the package make by Alien Bob (As expected).
It was fun to do, I am going to experiment with some other settings.
There are many tools Eric built that are at your disposal. many things have not caught up to Current but the tools are there.
Eric retired from LQ good and bad thing good is his translation of english seems to be very vulgar at times. Just like Pat's
But the tools are there neither one of them actually write code.
they are good at fixing stuff and that in it's self is a huge art.
Use the tools edit the tools fix the tools.
Grab a copy of his git and do it.
So if you think Pat or Eric write patches and contribute to the software you build show me one.
They are packagers Just like Willy like many other distro people.
They are nothing like SUSE maintainer that maintains ALSA.
There work is to create scripts build packages and hope some Dev does the work.
No more no less.
just good old people trying to make it work.
I didn't know Eric was gone. I'm usually the last to find out stuff like that. I will remember him for mastering very messy compiles
Libreoffice, which was never easy at the best of times.
Mesa, since they converted to that half-assed build system they're using.
Wine with the 64+32 bit build we take for granted but is very hard to set up in any other distro that I know of.
Multilib packages. I know he built on the work of the late Fred Emmot, but it's an excellent system.
His Live usb builds. I have one here with XFCE, Wine, and running a windows database program
He also is (Like Pat) a very capable bash scripter. Has anyone any idea what's going to happen to his repo on slackware.nl?
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,070
Rep:
As can be seen at https://alien.slackbook.org/blog/ Eric is still very much alive and active and maintains his repo. This week we've got updated packages of Chromium, Chromium-ungoogled, and LibreOffice among other stuff. But he has taken timeout from the Slackware team (and from LQ), now concentrating on what he himself maintains (including LiveSlak).
I had this happen several/many times with AlienBOB's LibreOffice and his other packages (VLC was another.) He implied read the SlackBuilds to determine dependencies. Is that really the only way possible to use AlienBOB's packages? I'd sooner use older packages from SlackBuilds.org builds that just work. Is there an easier way with AlienBOB's packages?
If you have the full slackware install, you have the needed dependencies. Otherwise, he mentions what you need. Slackware give you packages as the maintainer puts them up - complete with docs, libs, includes, & utilities. I tried skimping on the install, but it's easier to do it, then remove what is obviously crud.
The Bind package, for example, packages the nslookup utility. Other distros will strip the docs, includes, libs not used by the packaged binaries (but used in compiling) and have a smaller packages, and a smaller system. But if you want nslookup, that's another package. And good luck compiling anything. There's also a significant manpower overhead maintaining/updating packages.
I had this happen several/many times with AlienBOB's LibreOffice and his other packages (VLC was another.) He implied read the SlackBuilds to determine dependencies. Is that really the only way possible to use AlienBOB's packages? I'd sooner use older packages from SlackBuilds.org builds that just work. Is there an easier way with AlienBOB's packages?
I know that packages created by Alien Bob contain a "packagename.dep" file which contains a list of the dependent packages which you have to install from his repository additionally. I do not know how to automate the process of installing these dependencies but I habitually check for the existence of that file in the packages.
I had this happen several/many times with AlienBOB's LibreOffice and his other packages (VLC was another.) He implied read the SlackBuilds to determine dependencies. Is that really the only way possible to use AlienBOB's packages? I'd sooner use older packages from SlackBuilds.org builds that just work. Is there an easier way with AlienBOB's packages?
His packages also imply a fully-patched version of Slackware. If something has dependencies, he'll let you know what they are (like with obs-studio.) The dependencies of the dependencies are up to you to chase down.
I know that packages created by Alien Bob contain a "packagename.dep" file which contains a list of the dependent packages which you have to install from his repository additionally. I do not know how to automate the process of installing these dependencies but I habitually check for the existence of that file in the packages.
I couldn't find the packagename.dep--where are these?
I couldn't find the packagename.dep--where are these?
If a package has external dependencies which are not met by the Slackware distribution, there should be a .dep file in the same directory as the .txz package.
If you do not find such a .dep file, I expect that the package does not have external dependencies.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
