You are not logged in.
I have a doubt about the the rules of submission that I have for a while.
The first rule is:
The submitted PKGBUILDs must not build applications already in any of the official binary repositories under any circumstances. Check the official package database for the package. If any version of it exists, do not submit the package. If the official package is out-of-date, flag it as such. If the official package is broken or is lacking a feature, then please file a bug report.
It makes sense but I've seen multiple -git packages that don't include any changes compared with the official repository package (or at least they don't mention having any differences and the pkgname is the same).
Does this case not fall into that rule? What about -bin packages?
Last edited by justbispo (2026-05-16 16:16:16)
Offline
-git: obtaibs the latest version depend on the repos master branch
these can be identical if the latest release is the current commit on the master branch
but usually -git can be seen as "nightly", as in: it's the most recent version you can get no matter the current release
-bin: these obviously can't be in any binary repo as thier sole purpose is to provide pre-built binaries to skip the compiling step otherwise required for an aur package
there're also -git-bin combos which simply is what it sounds like: a pre-built binary of the latest repo master branch commit
Offline
Thanks, that clears up the -git packages. But I didn't understand your answer about -bin packages. When you say
these obviously can't be in any binary repo
do you mean foo-bin can't be in AUR because foo exists in the official repo?
Offline
-bin packages install prebuilt binaries (typically upstream provided), if that'd on rare occasion the same binary as provided by a repo package, the -bin package in the AUR cannot exist.
The more typical cases are that those applications aren't in the repo or the version in the repo was built downstream (raising a question about the point of having the -bin package in the AUR)
The gist is that you can have different iterations of the same software in the repos and the AUR (git, nightly upstream builds, …) but not the same iteration of the same software twice.
Offline
Ah that clarifies everything, thank you.
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline