From owner-freebsd-ports@FreeBSD.ORG Fri Oct 27 21:25:04 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35C5116A5CE; Fri, 27 Oct 2006 21:25:04 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60C9743D55; Fri, 27 Oct 2006 21:25:03 +0000 (GMT) (envelope-from itetcu@FreeBSD.org) Received: from it.buh.tecnik93.com (localhost [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id 0F2CC1711C; Sat, 28 Oct 2006 00:25:02 +0300 (EEST) Date: Sat, 28 Oct 2006 00:25:01 +0300 From: Ion-Mihai "IOnut" Tetcu To: "Andrew Pantyukhin" Message-ID: <20061028002501.32f5b845@it.buh.tecnik93.com> In-Reply-To: References: <20061027231646.5b07bd8f@it.buh.tecnik93.com> X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_JscxKdVN+hN9SYnHztD4USa; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Ion-Mihai IOnut Tetcu , Christopher Boumenot , freebsd-ports@freebsd.org Subject: Re: port_history - track port commit message comments X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 21:25:04 -0000 --Sig_JscxKdVN+hN9SYnHztD4USa Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 28 Oct 2006 01:04:05 +0400 "Andrew Pantyukhin" wrote: > On 10/28/06, Ion-Mihai IOnut Tetcu wrote: > > On Fri, 27 Oct 2006 16:26:54 +0400 > > "Andrew Pantyukhin" wrote: > > > > > On 10/27/06, Christopher Boumenot 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] >=20 > 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. The biggest problem is that it requires [a lot of] work for the commiter/submitter. The problem with the OP's work is that some submitters/commiters think that the CVS commit message should document the _port_ changes while others think it should also document (or at least provide pointers) to the changes in the software itself (I fall in the second category). Since we don't have a standard for this, relaying only on the CVS logs might drive one into nasty problems. And yes, some standards, one way or the other, or somewhere in between, whatever, as long as we're all __consistent__ would be very useful. One would know what to expect and what not to expect o find out from reading the CVS logs or files/UPDATING or whatever. From my POV it would be very nice to be able to read everything important for a port update from inside our Ports Tree, w/out having to go to the WWW site, etc.. > [Wow, man, dspam ports is sure a place to learn many > things :-) Great job!] Thanks. I'm pretty sure I re-invented the wheel a few times there; but overall I consider it to be one of the most user-friendly ports we have. We could _optionally_ support that kind of UPDATING file in our framework; and we also could support the check-options-version.=20 --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #188: ..disk or the processor is on fire --Sig_JscxKdVN+hN9SYnHztD4USa Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFQnktBX6fi0k6KXsRAnPdAJwItVkwgOVtTEZKitnoHENIH1OUbQCguqsd /ad7QRQjH5WurA+a7dMSLQs= =8Z6d -----END PGP SIGNATURE----- --Sig_JscxKdVN+hN9SYnHztD4USa--