Hi all,
It seems that the latest officially stable version of gsl (gnu scientific library) is 2.1. The repository is at 1.16, and I don't see anything more recent in [testing] or AUR.
Is there an intention to update this package straight to 2.1, or to introduce a gsl2 package? I've no problem with putting this on AUR myself, but I don't want to step on toes / waste time.
On Mon, 16 Nov 2015 00:38:04 -0500 (EST) Scott Lawrence bytbox@gmail.com wrote:
Hi all,
It seems that the latest officially stable version of gsl (gnu scientific library) is 2.1. The repository is at 1.16, and I don't see anything more recent in [testing] or AUR.
Is there an intention to update this package straight to 2.1, or to introduce a gsl2 package? I've no problem with putting this on AUR myself, but I don't want to step on toes / waste time.
gsl 2.0 was just released 2 weeks ago, and the Arch maintainer isn't the most active. Have patience.
Putting it in the AUR would just get it deleted. Rule 1 of the AUR is that it can't duplicate packages in the official repos.
On Sun, 15 Nov 2015, Doug Newgard wrote:
Putting it in the AUR would just get it deleted. Rule 1 of the AUR is that it can't duplicate packages in the official repos.
Okay. I figured that sometimes v2 and v1 become separate packages, so it might not count as a "duplicate", but I'll sit back and chill :)
If anyone else is wondering: there are no complications in changing the abs PKGBUILD to build v2.1, so it's easy enough to install on your own.
Thanks,
Scott
Doug Newgard wrote:
On Mon, 16 Nov 2015 00:38:04 -0500 (EST) Scott Lawrence bytbox@gmail.com wrote:
Is there an intention to update this package straight to 2.1, or to introduce a gsl2 package? I've no problem with putting this on AUR myself, but I don't want to step on toes / waste time.
gsl 2.0 was just released 2 weeks ago, and the Arch maintainer isn't the most active. Have patience.
Putting it in the AUR would just get it deleted. Rule 1 of the AUR is that it can't duplicate packages in the official repos.
IMO there are some cases when this is OK, for instance if the API changes in the new version are big enough that the update needs to be deliberately held back until all users have been ported. I'm not sure if this is the case here though, I haven't looked closely at the API changes, but I know there are at least a few KDE packages that don't build against gsl 2.
participants (4)
-
Antonio Rojas
-
Doug Newgard
-
Ralf Mardorf
-
Scott Lawrence