On Tue, May 03, 2005 at 07:44:45AM -0700, Link Dupont wrote: > On May 3, 2005, at 5:39 AM, Paul Mattal wrote: > > >This suggests to me that the easy middle ground to seek out is to > >share the unsupported PKGBUILD materials via cvsup but NOT as part of > >abs, and to put a simple tool in the aurtools package to fetch > >unsupported to a standard directory somewhere (like /var/unsupported). > >This would mean you couldn't use srcpac with it but you could at least > >fetch all the PKGBUILDs onto your system easily and efficiently, and > >then decide what to build and what not to build. > > If we're looking at a long term solution, and since you're already > looking at the idea of writing your own AUR distribution scripts, might > as well go all the way and write a srcpac-type script for the > /var/unsupported package tree. Maybe this could be further down the > road once the AUR "unsupported" fetch script is done, but its a > thought. > -Link
Not to nay-say the idea, but scripts like that would essentially be reimplementing pacman's update logic (or at least the majority of it). Especially if you wanted to support things like conflicts and provides. Plus, it'd be extra slow. Jason
pgpLpCYgKc63F.pgp
Description: PGP signature
_______________________________________________ arch mailing list arch@archlinux.org http://www.archlinux.org/mailman/listinfo/arch
