On Sun, Feb 27, 2011 at 03:37:59AM +0100, Rémy Oudompheng wrote: > On 2011/2/26 Justin Davis <[email protected]> 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
