Package Details: nng-git v1.0.1.55.g1c3350f6-1

Git Clone URL: https://aur.archlinux.org/nng-git.git (read-only)
Package Base: nng-git
Description: Rewrite of the SP protocol library known as libnanomsg
Upstream URL: https://nanomsg.github.io/nng/
Licenses: MIT
Conflicts: nng
Provides: nng
Submitter: vbmithr
Maintainer: vbmithr
Last Packager: vbmithr
Votes: 1
Popularity: 0.061051
First Submitted: 2018-05-16 17:58
Last Updated: 2018-08-26 14:38

Dependencies (4)

Required by (0)

Sources (1)

Latest Comments

vbmithr commented on 2018-07-10 23:46

Fixed, thanks.

MichaelChou commented on 2018-07-06 06:33

In build directory, libs* are symbolic links like this:

libnng.so -> libnng.so.1*
libnng.so.1 -> libnng.so.1.0.0*
libnng.so.1.0.0*

But the way of copying them in the package section of PKGBUILD makes 3 copies of the libs (not keeping the symbolic links), which is not the best. ldconfig complains about this as well when installing the built package.

vbmithr commented on 2018-07-05 07:31

Updated, thanks.

diraimondo commented on 2018-07-04 10:41

Maybe something has changed in the git tree after the release but I was not able to build the AUR package. It looks that in my system the 'build' subdir was missing on the build attempt. In order to get the package I had to add a mkdir in the prepare() step.

diraimondo commented on 2018-07-04 10:33

the first stable version 1.0 has been release, what about creating another AUR for the non-git version?

Thanks

vbmithr commented on 2018-06-04 09:18

I have updated the PKGBUILD. Hopefully the pkgver field will not change anymore. Thanks.

MichaelChou commented on 2018-06-04 08:43

The tag version format in git repo changed from 0.9.0.xx to something like v1.0.0.rc.1 (w/ a leading 'v'). And pacman considers the former newer than the latter which is obviously not the case:

$ vercmp v1.0.0.rc.1 0.9.0.35.g84c32ea
-1

You can solve this by either stripping the leading 'v' in pkgver() or add epoch=1 in PKGBUILD (https://wiki.archlinux.org/index.php/PKGBUILD#epoch)