Date: Fri, 27 Jan 2012 17:05:47 -0900 (AKST) From: rflynn@acsalaska.net To: "Matthew Seaman" <m.seaman@infracaninophile.co.uk> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Doing SQL to the FreeBSD ports index Message-ID: <3356.46.129.107.107.1327716347.squirrel@mymail.acsalaska.net> In-Reply-To: <4F199672.8050008@infracaninophile.co.uk> References: <4F199672.8050008@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Apropos nothing much at all, but congruent with some of the discussion > going on in this list at the moment, I've been playing around loading > ports index related data into a RDBMS and querying that to pull out > interesting factoids, or indeed a complete INDEX file. I didn't start > doing this with any idea other than my own edification but now it seems > it might be vaguely useful here and there, so I've stuck a copy on my > website: > > http://www.infracaninophile.co.uk/articles/portindexdb/ > > I'd be happy to hear from anyone using this, or receive bug reports / > feature requests. I haven't looked in detail - perl has to leave my head - but what I think is a good feature for a database to handle is to find outdated distfiles. Since the relationship between a portorigin and it's distfile(s) is not available otherwise. I realize portmaster uses /var/db/ports for it, yet if you share $PORTSDIR but not $PORT_DBDIR (different machines, different requirements) then this method gets ugly fast. Quick parse of distinfo should do the trick. Record the hash and you can get bonus points for indicating hash errors (incomplete aborted downloads or upstream changed distfile). -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3356.46.129.107.107.1327716347.squirrel>