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.
Why --enable-avahi in libreoffice for -current when avahi does not ship in -current?
I don't understand how those two things are necessarily connected. Many SBo SlackBuilds use other SBo packages (and specify them in the REQUIRES field of the .info file) when those packages don't ship in -current (or whatever you're building for).
If you really just don't like avahi, that is a different question.
If you just want a 'minimal build' then, while I understand the idea, I don't subscribe to it by default. I generally prefer to expose all the features the developers have released, including the kitchen sink, if available. If I were building for some esoteric device with minimal resources, it would almost certainly be otherwise; however my target is a pretty normal desktop - I can enjoy the fully featured version.
I just checked that the --enable-avahi option could be removed and the build would still complete. Your final product would not then have whatever functionality avahi provides for LibreOffice. I'm not in a position to itemize all that functionality but my first guess would be printer discovery to output your documents.
If I were building for some esoteric device with minimal resources, it would almost certainly be otherwise; however my target is a pretty normal desktop - I can enjoy the fully featured version.
Well, my opinion is that if you're going to pull dependencies from outside of the main tree, you could at least make them optional.
I'll share this simple snippet for firefox slackbuild that I wrote for making official branding optional:
Code:
if [ "$OFFICIAL" = "yes" ]; then
echo "ac_add_options --enable-official-branding" >> .mozconfig
else
echo "ac_add_options --disable-official-branding" >> .mozconfig
fi
It's an example of setting defaults in a transparent way, so that the users know what is tested & confirmed optional and what is not.
Like or dislike for particular implementation has nothing to do with it, I would not comment at all if you hadn't tried to make it look like mandatory external dependency.
Either way, it's your git, I don't really care about your dependencies, and I won't discuss the usefulness of avahi on systems using static routes.
Just use my script if you want to choose your own optional dependencies with libreoffice, that is why it was made...
The only dependency libreoffice needs that is not included in Slackware is perl-Archive-Zip. Also, its still not at all cool to have a libreoffice script that compiles experimental features by default (VLC).
Edit:
Code:
--enable-vlc Enable building with the (experimental) VLC avmedia backend.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
