I didn't even know avahi could mean that... Please see willysr's link. :)

Edit: Avahi is also a genus for wooly lemurs. I think that is the definition I want to remember from now on.

https://en.wikipedia.org/wiki/Woolly_lemur

I'd take a SlackBuild for a recent netatalk.

As far as Avahi, what can you say to sell it? How does it behave, for example, if binaries are linked to the library but the admin has chosen not to run the daemon?

Probably best to start with that netatalk.SlackBuild. I'm at volkerdi @ slackware dot youknowwhat.

That AVAHI is the mountain where stops the the generic desktop/server usage of a Linux distribution and behind it is only desktop.

That AVAHI may look fancy and cute for The Church of Apple followers, BUT I for one, I will prefer the Slackware without it. :hattip:

He talks about A.H.A.V.I., like you written previously, BTW... ;)

did Slackware recently got PAM? this would be great!
because I do not think it is possible to build netatalk without PAM, since it is extra listed in the build requirements.

edit: just see it's listed optional, so should be possible without PAM

nss-3.37.1:

https://developer.mozilla.org/en-US/..._release_notes
https://ftp.mozilla.org/pub/security...-3.37.1.tar.gz

Pat,

Slackbuild for netatalk is in your email.

schu

hplip-3.18.5:

https://developers.hp.com/hp-linux-i.../release_notes
https://datapacket.dl.sourceforge.ne...-3.18.5.tar.gz

php-7.2.6:

http://php.net/ChangeLog-7.php#7.2.6
http://php.net/downloads.php

nfs-utils-2.3.2:

https://mirrors.edge.kernel.org/pub/...s-2.3.2.tar.xz

Would it be possible that with time this or an equivalent line from the slackbuilds.org templates could be added to every SlackBuild in the main tree?
There have been many times I have wanted to look at a SlackBuild to gain insight on the build process and discovered it was missing from the documentation directory. This of course means I have to go grab it from the source tree or find it on a web browser which is slightly annoying. :)

One arbitrary example is zsh, but there are many others too.

Edit: One downside of looking in the source tree is that the SlackBuild may have changed since the installed package was created and may not necessarily be the same.

and this my friends is the strength of Slackware!

I will add one upvote for your request :-)

I would also like to see this happen.

And one downvote. I can't see the point. They're just a 'curl/wget' away if you want them.

Last I checked the Slackware is a distribution shipped as binary packages, and precisely it is not Gentoo!

I believe that those who want to study the Slackware's sources, should look into "source" directory and that's all folks!