[aur-general] PKGBUILD URL has changed
I just wanted to let AUR helper authors (or other AUR enthusiasts) know that the PKGBUILD URL has changed on the AUR. All AUR helpers should update your code. I knew the AUR was updated recently but I did not realize that the URLs were changed for PKGBUILDs until I looked carefully at the AUR and the new patches. I found out earlier today and wanted to help others who might wonder why their AUR software slowly starts to break. The old scheme was: /packages/<name>/<name>/PKGBUILD The new scheme is: /packages/<name>/PKGBUILD Fun facts: Packages that were uploaded before the change still have an extracted package directory (/packages/<name>/<name>). The old packages also have a copy of their PKGBUILD in the new location.This means they have a PKGBUILD in both locations. Once a package is uploaded the old package directory is deleted so only one PKGBUILD remains (/packages/<name>/PKBUILD). So all packages uploaded after the change use the new PKGBUILD URLs. -juster
On 2011/2/26 Justin Davis <jrcd83@gmail.com> wrote:
I just wanted to let AUR helper authors (or other AUR enthusiasts) know that the PKGBUILD URL has changed on the AUR. All AUR helpers should update your code. I knew the AUR was updated recently but I did not realize that the URLs were changed for PKGBUILDs until I looked carefully at the AUR and the new patches. I found out earlier today and wanted to help others who might wonder why their AUR software slowly starts to break.
The old scheme was: /packages/<name>/<name>/PKGBUILD The new scheme is: /packages/<name>/PKGBUILD
The URL for tarballs is /packages/$name/$name.tar.gz and I don't think this has ever changed in the past months I don't think anyone is downloading mere PKGBUILDs and doing anything useful with that: PKGBUILDs are useless without their associated files. -- Rémy.
On Sun, Feb 27, 2011 at 03:37:59AM +0100, Rémy Oudompheng wrote:
On 2011/2/26 Justin Davis <jrcd83@gmail.com> wrote:
I just wanted to let AUR helper authors (or other AUR enthusiasts) know that the PKGBUILD URL has changed on the AUR. All AUR helpers should update your code. I knew the AUR was updated recently but I did not realize that the URLs were changed for PKGBUILDs until I looked carefully at the AUR and the new patches. I found out earlier today and wanted to help others who might wonder why their AUR software slowly starts to break.
The old scheme was: /packages/<name>/<name>/PKGBUILD The new scheme is: /packages/<name>/PKGBUILD
The URL for tarballs is /packages/$name/$name.tar.gz and I don't think this has ever changed in the past months
I don't think anyone is downloading mere PKGBUILDs and doing anything useful with that: PKGBUILDs are useless without their associated files.
--
This isn't dealing with tarballs. This is strictly for the extracted PKGBUILDs that have _always_ existed at /packages/$name/$name/PKGBUILD. I've been downloading from that URI for nearly a year now and only today I noticed it was broken after Justin kindly pointed it out to me. If you run 'cower -ii <pkg>', cower performs a second request explicitly to get the PKGBUILD and parse out extra information like depends, makedepends, replaces, optdepends... I'm not alone here. I know brisbin's aurget allow fetching PKGBUILDs just for previewing, and I'm fairly sure that yaourt has a similar feature. This is _definitely_ something that is used. Those PKGBUILDs have value on their own. dave
On Sat, Feb 26, 2011 at 04:37:19PM -0500, Justin Davis wrote:
I just wanted to let AUR helper authors (or other AUR enthusiasts) know that the PKGBUILD URL has changed on the AUR. All AUR helpers should update your code. I knew the AUR was updated recently but I did not realize that the URLs were changed for PKGBUILDs until I looked carefully at the AUR and the new patches. I found out earlier today and wanted to help others who might wonder why their AUR software slowly starts to break.
The old scheme was: /packages/<name>/<name>/PKGBUILD The new scheme is: /packages/<name>/PKGBUILD
Fun facts: Packages that were uploaded before the change still have an extracted package directory (/packages/<name>/<name>). The old packages also have a copy of their PKGBUILD in the new location.This means they have a PKGBUILD in both locations. Once a package is uploaded the old package directory is deleted so only one PKGBUILD remains (/packages/<name>/PKBUILD). So all packages uploaded after the change use the new PKGBUILD URLs.
Those leftover files from the old extraction scheme should be gone now.
participants (4)
-
Dave Reisner
-
Justin Davis
-
Lukas Fleischer
-
Rémy Oudompheng