1. net-misc/nxclient version bump from 3.2.0-9 to 3.2.0-13 2. the ebuild naming convention is 3.2.0, and installs 3.2.0-9. The distributor now uses an additional digit; e.g. 3.2.0-13. Perhaps the ebuild naming convention should be changed? 3. The same naming convention issue exists with nxserver and nxnode. nxserver and nxnode are currently up to date in portage. http://www.nomachine.com/download-package.php?Prod_Id=4 Reproducible: Always
Thanks for the report, but nxclient-3.2.0-r1 ebuild (which uses -13 source) is already in the tree It's still on my TODO list though to make the maintenance release number more visible in the ebuild, but this will require some $PV manipulation (3.2.0-13 is not a valid version). Patches are welcome of course ;)
"Thanks for the report, but nxclient-3.2.0-r1 ebuild (which uses -13 source) is already in the tree" Heh.... you must have had that in there within minutes of the new release. I saw r1 later the same day and couldn't comprehend that it included the new version. "It's still on my TODO list though to make the maintenance release number more visible in the ebuild, but this will require some $PV manipulation (3.2.0-13 is not a valid version). Patches are welcome of course ;)" (newbie) 1. Patches? Does that mean that a reporter posts a new ebuild? It might be more headache for you than doing it yourself (though I could at least get the hashes for the manifest, I guess). 2. what does $PV mean?
(In reply to comment #2) > (newbie) > 1. Patches? Does that mean that a reporter posts a new ebuild? It might be more > headache for you than doing it yourself (though I could at least get the hashes > for the manifest, I guess). Some reporters post great ebuilds ;) But it's true that for nx, I'll probably write it up myself > 2. what does $PV mean? It's the variable set to the package version in the ebuild: http://devmanual.gentoo.org/ebuild-writing/variables/index.html The trick here will be to use something for the ebuild like 3.2.0.9, and then manipulate the string to get the correct 3.2.0-9 (for tarball) and 3.2.0 (for path in the archive).
Hey! ..... you work quickly!! Just noticed your new ebuild, and the new naming convention makes sense to me (newbie)!! Thank You. Now the bad news; they just released client 3.2.0-14. I marked this as reopened in case you don't get comments about resolved/fixed bugs......
Strange, they did not send the usual e-mail for this one (which is the only way to get the release notes/changelog). And it's not available for amd64... I've asked NoMachine what this release is about
They favor -14 on x86, so I've added it to portage (no amd64 keyword, as it does not exist for this release). Thanks for the bugreport!
