Date: Tue, 30 Nov 2010 18:58:10 +0000 From: David Southwell <david@vizion2000.net> To: freebsd-ports@freebsd.org Subject: Re: Ports - installation & upgrade history Message-ID: <201011301858.11175.david@vizion2000.net> In-Reply-To: <3B286D1E-E7F8-4FF5-85E9-29309A8693C6@mac.com> References: <201011301824.15550.david@vizion2000.net> <201011301841.35462.david@vizion2000.net> <3B286D1E-E7F8-4FF5-85E9-29309A8693C6@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 30, 2010, at 10:41 AM, David Southwell wrote: > > I was thinking of something which is far more comprehensive and > > systematic. Whilst installed options are obtained by examining > > /var/db/ports the files do not do not provide the detailed historical > > information which I envisage. > > Correct. Unless you've taken good backups, nothing else currently > preserves all of the historical information you envision, but you can at > least get some of the requested info just out of the current filesystem. > > > The freshports/freebsd sites will tell us when the distributed ports tree > > was changed but does not provide a historical record of changes to the > > local ports tree. > > Also correct. Again, short of having periodic backups made at sufficiently > rapid intervals, there is no way to track that information over time. > > Regards, Seems to me that a comprehensive record would be extremely useful on a local system. I am wondering how difficult it might be to collect data from applications such as: cvsup of ports tree portupgrade/portmaster changes to /var/db/ports changes to /usr/ports/distfiles The results could be held in a mysql database. David Photographic Artist Permanent Installations & Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography & Official Portraiture Combined darkroom & digital creations & Systems Adminstrator for the vizion2000.net network
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011301858.11175.david>