Package Details: lib32-avahi 0.7+18+g1b5f401-1

Git Clone URL: https://aur.archlinux.org/lib32-avahi.git (read-only)
Package Base: lib32-avahi
Description: Service Discovery for Linux using mDNS/DNS-SD -- compatible with Bonjour (32-bit)
Upstream URL: https://github.com/lathiat/avahi
Licenses: LGPL
Submitter: Medved
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 146
Popularity: 0.90
First Submitted: 2010-10-29 15:45
Last Updated: 2019-06-12 02:17

Latest Comments

« First ‹ Previous 1 2 3 4 5 6

Medved commented on 2011-03-19 07:55

@Sansui350A, no need to write manuals here - just flag the package Out-of-date (there is a button) and I'll get a notification and take care.

Anonymous comment on 2011-03-19 01:33

You need to edit this PKGBUILD's download url to: http://archlinux.mirrors.ovh.net/archlinux/extra/os/i686/avahi-0.6.29-1-i686.pkg.tar.xz, download it, run md5sum downloadedpkghere, and replace the md5sum in the PKGBUILD with the one generated from the md5sum command.. also, sorry for any typo's, as this was done from my lappy at a WEIRD angle.. xD Hope this helps everyone, 'specially those who use the Phoenix Viewer for SL.

Medved commented on 2011-02-04 20:43

PS: I used to be a Gentoo geek for more than 2 years, and I must agree that building everything on your own has some advantages. But that is the "Gentoo way". The "portage" and it's "USE flags" has its own beauty. But don't try to transform Arch into a Gentoo-like distro - it's a bad idea.

Medved commented on 2011-02-04 20:37

Now the libraries are copied to /usr/lib32
However, I'm not building the package from source as many of you guys sugested.
First of all the build fails beause of some 32-bit libraries and I'm not in the mood to debug that.
Second I don't agree with the "build from source" policy at all. I already argued my point of view in some private mails, but I'll do it one more time, just to cald down the spirits. So, here's why I DON'T AGREE and DON'T LIKE this "policy":
1. It takes time&resources for the user.
2. Dependency for 'gcc-multilib', package that is not required by most
regular users.
3. The build may fail in some code, which may require manual patches.
4. The new binaries aren't tested, which means potential bugs.

Don't forget that Arch tries to "Keep It Simple". Why do some geeks like to complicate things so much? And what's the gain for (re)building? What's the cash?

Anonymous comment on 2011-01-09 16:41

Please update your PKGBUILD(s) to reflect the new lib32 multilib standards. /opt/lib32 is no longer valid; the new location is in /usr/lib32 and has been for months. This change really should be reflected onto all of your lib32 PKGBUILD(s). Also PKGBUILD really should pull from source these days and compile, instead of pulling precompiled i686 binaries from the Arch repos as this method is highly discouraged. :)

whaler commented on 2010-11-27 15:15


The source package - 0.6.27-7-i686.pkg.tar.xz - is missing. How come?