cmbrannon at cox.net
Tue Nov 11 19:13:24 EST 2008
"Aaron Griffin" <aaronmgriffin at gmail.com> writes:
> is related to the AUR backend daemon (tupkgupdate ?), which is in the
> AUR repository. A rewrite would be HUGELY appreciated.... the steps
> are simple: find new packages in upload dir, add to pacman DB, add to
> mysql DB. It's not all that hard, yet the current daemon runs through
> ALL packages when it does this, IIRC
I had a look at the tupkgupdate code. The main source of I/O seems to be
the following loop:
a_files = pkgbuildsInTree(pkgbuild_dir)
for a_file in a_files:
pkgname, ver, desc, url, depends, sources, category = \
infoFromPkgbuildFile forks and execs bash to process a PKGBUILD.
All of the code that deals with binary packages only extracts
information from filenames, as far as I can tell.
Would it be reasonable to use timestamps to determine which packages
have been updated?
More information about the aur-dev