Date: Sat, 28 Oct 2006 01:04:05 +0400 From: "Andrew Pantyukhin" <infofarmer@FreeBSD.org> To: "Ion-Mihai IOnut Tetcu" <itetcu@freebsd.org> Cc: freebsd-ports@freebsd.org, Christopher Boumenot <boumenot@gmail.com> Subject: Re: port_history - track port commit message comments Message-ID: <cb5206420610271404hbb3ba6an99377535ebe1af98@mail.gmail.com> In-Reply-To: <20061027231646.5b07bd8f@it.buh.tecnik93.com> References: <ehs1qk$6pa$1@sea.gmane.org> <cb5206420610270526p56bf0457i8e780b948a392d05@mail.gmail.com> <20061027231646.5b07bd8f@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/28/06, Ion-Mihai IOnut Tetcu <itetcu@freebsd.org> wrote: > On Fri, 27 Oct 2006 16:26:54 +0400 > "Andrew Pantyukhin" <infofarmer@FreeBSD.org> wrote: > > > On 10/27/06, Christopher Boumenot <boumenot@gmail.com> wrote: > > > Every time I upgrade a port I am usually left wondering what > > > changed. > > > > Some other projects maintain special package-specific > > ChangeLog files. Maybe VCS logs is not the best place > > for documentation, because it's not as easily accessible > > as a flat file would be. > > > > Moreover, I think porters don't document the hacks they > > have to employ - just because there's nowhere to do that. > > You all might want to take a look at what I do in > mail/dspam[-devel]/[Makefile|files/UPDATING] Yes, the idea is very bright. There's no rush however, so let's look at how other people deal with it, among ports committers and outside, before we set any standards in stone. [Wow, man, dspam ports is sure a place to learn many things :-) Great job!] Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420610271404hbb3ba6an99377535ebe1af98>