Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Oct 2006 21:54:22 +0300
From:      Ion-Mihai "IOnut" Tetcu <itetcu@FreeBSD.org>
To:        hans@lambermont.dyndns.org (Hans Lambermont)
Cc:        freebsd-ports@freebsd.org
Subject:   Re: port_history - track port commit message comments
Message-ID:  <20061028215422.625289f5@it.buh.tecnik93.com>
In-Reply-To: <20061028181646.GG19996@leia.lambermont.dyndns.org>
References:  <ehs1qk$6pa$1@sea.gmane.org> <cb5206420610270526p56bf0457i8e780b948a392d05@mail.gmail.com> <20061027231646.5b07bd8f@it.buh.tecnik93.com> <cb5206420610271404hbb3ba6an99377535ebe1af98@mail.gmail.com> <20061028002501.32f5b845@it.buh.tecnik93.com> <20061028181646.GG19996@leia.lambermont.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_V9mZi3QJyCrQEM2b090XI8v
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sat, 28 Oct 2006 20:16:47 +0200
hans@lambermont.dyndns.org (Hans Lambermont) wrote:

> Ion-Mihai IOnut Tetcu wrote:
>=20
> ...
> >>>> On 10/27/06, Christopher Boumenot wrote:
> >>>>> Every time I upgrade a port I am usually left wondering what
> >>>>> changed.
> ...
> > 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.
>=20
> But it is much better than what we have now (nothing) and I think that
> having a system like what Christopher proposed probably leads to
> establishing a standard (preferably of the second category :) .

Christopher's work is indeed valuable and I should have mentioned this
in my first post :(

I'm afraid of a partial solution because one tends to relay (only) on
it and, since it partial, tends nt to check the vendor site, README,
CHANGES or UPDATING included in the tarbal, etc.

A similar thing drives me mad each time I install a new machine and I
discover I have to recurse in the dependency tree of the ports I need
because some of them don't have OPTIONS.

> If the information is easily available I think it will be used.

One has to be optimistic about it, albeit the opposite example provided
by people not reading UPDATING ;-)


--=20
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"

BOFH excuse #138:
BNC (brain not connected)



--Sig_V9mZi3QJyCrQEM2b090XI8v
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFQ6djBX6fi0k6KXsRAijwAKCWaKBiowvic1jPPK2/lJOtfxm+uQCgmnGF
thv5xdVTFdxZGQ8uOWXvyOo=
=GaI/
-----END PGP SIGNATURE-----

--Sig_V9mZi3QJyCrQEM2b090XI8v--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061028215422.625289f5>