On Sun, 13 Sep 2009 19:57 -0000, villa.alberto wrote:
hello! encouraged by a request, i've written this small utility (attached) to show the commit history for a port (using freshports.org), and i was wondering... how about adding this functionality to portmaster? here's an example of its output: $ ./portchangelog.sh editors/vim ===>>> Gathering commit history for editors/vim ===>>> Number of commits found: 220 (showing only 100 on this page) =================>>> 29 Jul 2009 21:19:43 >> 7.2.239 Committer: w...@freebsd.org Chase patch rename so that it passes "make checksum" =================>>> 29 Jul 2009 08:40:23 >> 7.2.239 Committer: obr...@freebsd.org Change name of diked patch. at the moment it is a bit rough (it is just a shell script), but i can make it more serious if wanted (eg. not using a " " to identify a field) so... what do you think about this?
I don't see this as a necessary addition. For one portmaster is a shell script. For two it means that the upgrade always needs to be connected and able to connect to the freshports site. For three freshports is just an 3rd party site where as you can get commit info right from the FreeBSD.org repo's. Four I don't see why anyone needs the commit info at upgrade time because as a part of administration this should be taken care of before you decide to upgrade anything.
Best regards. -- Jason J. Hellenthal http://www.DataIX.net/ jas...@dataix.net 0x691411AC - (2^(N-1)) _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
