Package Details: sdl3-git 3.1.6.r28.g908bd84c5-1

Git Clone URL: https://aur.archlinux.org/sdl3-git.git (read-only, click to copy)
Package Base: sdl3-git
Description: Simple Directmedia Layer (Version 3)
Upstream URL: https://www.libsdl.org
Licenses: zlib
Conflicts: sdl3
Provides: sdl3
Submitter: VitalyR
Maintainer: VitalyR (HurricanePootis)
Last Packager: HurricanePootis
Votes: 3
Popularity: 0.077274
First Submitted: 2023-06-29 19:11 (UTC)
Last Updated: 2024-11-07 23:55 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

yataro commented on 2024-06-28 00:38 (UTC) (edited on 2024-06-28 00:41 (UTC) by yataro)

I guess you are confused because there is no explicit version in provides, but this is not needed as this package provides sdl3 and version WILL come from $pkgver. Any package that does blasphemy by depends=('sdl3>=3.1.2') (let's say hypothetically there is git tag with version 3.1.2 but no prerelease with version 3.1.1) WILL work fine because this package (hypothetically) already provides sdl3=3.1.2.

yataro commented on 2024-06-28 00:28 (UTC)

I give up, I don't understand why you ignore the fact that there is no 3.1.2 version at all... Your link to the wiki is completely unrelated. End users should not be pinning to any SDL3 version yet.

What is the point of adding provides with $pkgver if implicit provides already includes it and $pkgver is usually equal to pkgver from sdl3 OR broken.

You're ignoring everything I'm pointing out.

abouvier commented on 2024-06-28 00:16 (UTC) (edited on 2024-06-28 00:21 (UTC) by abouvier)

Anyway, this is what is officially recommended.

The fact that the upstream version is wrong/unreliable/unstable is irrelevant because $pkgver will always track the current version they have chosen and thus will be correct.

This package is just out-of-date.

yataro commented on 2024-06-27 21:26 (UTC)

The "version" of this package is actually 3.1.1, and using provides as a workaround to force the use of another package is completely wrong. Why would you provide a non-existent version? There's no more 3.1.2.

This is a git package, is this sane to change commits and track every update or to generate provides using tag info that is unstable for SDL3 and should not be used to keep it working? And again, tags were removed and version was pushed back from 3.1.2 to 3.0.0, then updated to 3.1.1.

The version of the package should be 3.0.0, tags are only used for development.

abouvier commented on 2024-06-27 21:16 (UTC)

I'm not responsible for the versions on which packages chose to depend on. And good provides array makes the switch automatic.

yataro commented on 2024-06-27 21:05 (UTC) (edited on 2024-06-27 21:07 (UTC) by yataro)

sdl3 package is wrong and it does not make sense to depend on these versions. If you want to use the latest SDL3, just depend on sdl3-git, after SDL3 gets real releases you can switch to plain sdl3.

yataro commented on 2024-06-27 21:03 (UTC)

sdl3-git version after build is 3.1.1, see my previous comment. Tags have been deleted and can be deleted again. Please, see https://github.com/libsdl-org/SDL/issues/9952#issuecomment-2145677263 for why you should not depend on SDL3 prereleases

abouvier commented on 2024-06-27 20:56 (UTC) (edited on 2024-06-27 20:57 (UTC) by abouvier)

@yataro A sdl3 package (in version 3.1.1) is available on the AUR. The purpose is to force a dependence on sdl3-git (when a package needs the latest changes) by using sdl3>3.1.1

yataro commented on 2024-06-27 20:33 (UTC)

@abouvier There are no releases for SDL3, the versioning can change at any time and has already changed once This kind of change serves no purpose and is prone to errors

abouvier commented on 2024-06-27 15:52 (UTC)

Can you add provides=("sdl3=$pkgver")? It will allow other packages to do e.g. depends=('sdl3>=3.1.2').

« First ‹ Previous 1 2 3 Next › Last »