You are not logged in.
Pages: 1
Hi all,
I'm not sure that this is the proper subforum, but hopefully it's not too far off.
I'm a user of the 'bzr' bazaar package and it's fallen out of date in Extra. So I thought, I'm a programmer! I should be able to build a new package!
And I did, but now that I did I'd like to share it so that those using it can upgrade to this version, only I don't know /how/ to give the package (or just the PKGBUILD) file so that it can be updated in "Extra" (where it currently lives)
Any suggestions/pointers for where to go?
EDIT: Apparently someone updated it just today - 8 minutes ago, in fact.
Last edited by nborrelli (2010-06-13 18:14:47)
Offline
I don't have a clue about this particular package (I vaguely know what it does, though). You should load that up to AUR. If it is good, a TU may come along and push it to [community]. If it is really good, a Dev may come along and push it to [extra].
At least, this is my basic understanding of workflow:D But it will not be recognized unless you publish it.
Offline
No, packages that are already in [extra] should not go to AUR.
Offline
Why not? There are plenty of examples for the opposite. svn, beta etc packages definitely find their place in the AUR.
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
For reference, the correct approach make sure the package is flagged out of date and to email either the maintainer or the arch-general list with the updated PKGBUILD (if there is substantial changes).
Offline
Why not? There are plenty of examples for the opposite. svn, beta etc packages definitely find their place in the AUR.
svn-packages and the like are something diefferent, especially because their names differ from of the name of the package in extra. Putting something into AUR that is just a version bump of the version in on of the repos is strictly forbidden.
Offline
Pages: 1