On Tue, Oct 6, 2009 at 1:52 PM, Laszlo Papp <djszapi@archlinux.us> wrote:
On Tue, Oct 6, 2009 at 1:40 AM, elij <elij.mx@gmail.com> wrote:
I guess I don't see the need for this. If you want to see 'new packages', just use the rss feed. Dumping this in the rcp api seems... wrong to me.
Hello Elliot!
Thank you the feedback! My opinion in this matter is that if I'd like to create a frontend program for AUR, especially console based e.g., or to create another API/backend for AUR, then the json interface/output would be more portable than parsing html/xml pages to get an option for a command line frontend to get the newly submitted/updated packages.
Rss feed and this option are different purposes in fact. With this option from command line you could get anytime the newly updated/submitted packages, but with rss you see them continously. The first facility is really console based, but the second is webpage based, I think it's different or maybe I'm wrong.
You could do the exact same thing with an RSS feed... I don't understand how this data being in RSS makes it so that you cannot fetch the results whenever you want. RSS isn't made of magic. $ cat aurpkgs.py #!/usr/bin/env python import feedparser pkgs=feedparser.parse("http://aur.archlinux.org/rss2.php") print pkgs.feed.title for i in pkgs.entries: print i.title $ python aurpkgs.py AUR Newest Packages munipack rawtran fitspng sloppy lib32-jack-audio-connection-kit lib32-libsndfile lib32-flac perl-proc-pid-file libcss-svn libwapcaplet-svn vpipe aircrack-ng-cuda perl-compress-zlib generatorrunner haskell-vty-ui lua-md5 haskell-bindings-libcddb geda-gaf haskell-sample-frame gdatacopier-svn