[aur-general] Delete request
Hi all angband-svn http://aur.archlinux.org/packages.php?ID=33018 epiar-cvs http://aur.archlinux.org/packages.php?ID=20735 switched since some time to git opensnc http://aur.archlinux.org/packages.php?ID=40910 is a duplicate of opensonic http://aur.archlinux.org/packages.php?ID=25598 rrootage-data http://aur.archlinux.org/packages.php?ID=10842 is an incomplete outdated clone of rrootage http://aur.archlinux.org/packages.php?ID=10843 My addition question: what to do with epiar? The original package http://aur.archlinux.org/packages.php?ID=958 has been flagged out of date (correctly) since many new version came out. the problem is that upstream resetted the version counter, and is at 0.4.1: much newer than actual package, but version number inferior... What would the good way to update this? Create a new package like epiar-new or make epiar return to 0.4.1? I fear the second would cause AUR helpers to not upgrade existing installations of epiar...
On 09/27/2010 09:40 PM, Luca Bennati wrote:
Hi all
angband-svn http://aur.archlinux.org/packages.php?ID=33018 epiar-cvs http://aur.archlinux.org/packages.php?ID=20735 switched since some time to git
opensnc http://aur.archlinux.org/packages.php?ID=40910 is a duplicate of opensonic http://aur.archlinux.org/packages.php?ID=25598
rrootage-data http://aur.archlinux.org/packages.php?ID=10842 is an incomplete outdated clone of rrootage http://aur.archlinux.org/packages.php?ID=10843 Done, thanks. My addition question: what to do with epiar? The original package http://aur.archlinux.org/packages.php?ID=958 has been flagged out of date (correctly) since many new version came out. the problem is that upstream resetted the version counter, and is at 0.4.1: much newer than actual package, but version number inferior... What would the good way to update this? Create a new package like epiar-new or make epiar return to 0.4.1? I fear the second would cause AUR helpers to not upgrade existing installations of epiar...
Good question. In a repo package, the 'force' option (see 'man pkgbuild') would be the correct solution. I don't know if any AUR helpers handle it correctly though.
On Mon, Sep 27, 2010 at 15:59, Jakob Gruber <jakob.gruber@gmail.com> wrote:
On 09/27/2010 09:40 PM, Luca Bennati wrote: Good question. In a repo package, the 'force' option (see 'man pkgbuild') would be the correct solution. I don't know if any AUR helpers handle it correctly though.
None of the AUR helpers will handle this
On Mon, Sep 27, 2010 at 15:59, Jakob Gruber <jakob.gruber@gmail.com> wrote:
On 09/27/2010 09:40 PM, Luca Bennati wrote: Good question. In a repo package, the 'force' option (see 'man pkgbuild') would be the correct solution. I don't know if any AUR helpers handle it correctly though.
None of the AUR helpers will handle this
Before anyone asks, the reason that none of the AUR helpers handle this is that the JSON interface does not include information about the "force" flag. The only way to determine that would be to download the PKGBUILD, which would mean that every time you checked for updates, it would have to download PKGBUILDs for all AUR packages to be sure, which would be very wasteful.
2010/9/27 Daenyth Blank <daenyth+arch@gmail.com <daenyth%2Barch@gmail.com>>
On Mon, Sep 27, 2010 at 15:59, Jakob Gruber <jakob.gruber@gmail.com> wrote:
On 09/27/2010 09:40 PM, Luca Bennati wrote: Good question. In a repo package, the 'force' option (see 'man pkgbuild') would be the correct solution. I don't know if any AUR helpers handle it correctly though.
None of the AUR helpers will handle this
I think I have found the 3rd possible (and probably best) way: according to http://epiar.net/trac/roadmap the new 0.5 version will come out very soon: the mantainer could simply raise the pkgrel (adapting the PKGBUILD to new course) and solve the update tech problem :) if mantainer is not interested, since from 2008 he didn't take action, i can adopt it, but i will wait for version to come out and will contact him about it before.
participants (4)
-
Daenyth Blank
-
Jakob Gruber
-
Luca Bennati
-
Xyne