Re: [opensuse-packaging] Force specific Lua version as build requirement
Hello Axel, "Dr. Axel Braun" <axel.braun@gmx.de> writes:
However, doesn't it make sense to add provides: lua53 to the Lua package to avoid this hassle in future?
Not sure if I understand your approach. I think that does not make sense - you can always derive the version from the package. What do you mean with _derive_?
However, I will try to explain my thoughts: The current naming scheme of the Lua packages is - lua for the latest version at the time point when the openSUSE version was released - lua50, lua51, etc. for all older Lua versions Thus for example in openSUSE 13.2 lua package = Lua 5.2.x lua51 package = Lua 5.1.x lua50 package = Lua 5.0.x Now in Tumbleweed and Factory we have lua = Lua 5.3.x lua52 = Lua 5.2 lua51 = Lua 5.1.x lua50 = Lua 5.0.x This naming scheme is also explained in https://en.opensuse.org/openSUSE:Packaging_Lua#Addon_packages As a consequence, packagers have to fiddle with %if-suse_versions every time when the Lua versions increases. Additionally, in the period where Factory had already upgraded the Lua version and Tumbleweed not, one of them failed to build. My suggestions is to name in Tumbleweed and Factory the lua package also lua53. This would make the life easier because if you have to package a program which requires lua53 you can just write BuildRequires: lua53-devel and it will stick to that version. I don't know if naming the latest lua package also lua53 has any side effect. However, when upgrading to Lua 5.4, it will be named lua53 anyway. Best regards, Heinz "Dr. Axel Braun" <axel.braun@gmx.de> writes:
Hello Heinz,
Am Montag, 27. Juli 2015, 11:42:05 schrieb Green Basilisk:
I think the problem vanished because now Tumbleweed and Factory are aligned in terms of Lua versions. :)
However, doesn't it make sense to add provides: lua53 to the Lua package to avoid this hassle in future?
Not sure if I understand your approach. I think that does not make sense - you can always derive the version from the package. Except you want to replace lets say the gizmo-package with the more advanced gizmo-turbo. Then you could add a prevides: gizmo > (a version higher than the current gizmo package) to gizmo-turbo to force the change
Cheers Axel
-- Dr.-Ing. Axel K. Braun Mobile: +49.173.7003.154 VoIP/Skype: axxite PGP Fingerprint: CB03 964D 1CFA E87B AA63 53F3 1BD6 F53A EB48 EF22 Public Key available at http://www.axxite.com/axel.braun@gmx.de.asc
This mail was *not scanned* before sending. It was sent from a secure Linux-Desktop:
ThinkPad T520 OS: openSUSE 13.1 (x86_64) Kernel: 3.11.10-29-desktop KDE: 4.14.10 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (1)
-
Green Basilisk