Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Dec 2003 15:27:23 +0100
From:      Erwin Lansing <erwin@FreeBSD.org>
To:        doc@FreeBSD.org
Subject:   Re: Documentation of major changes to the ports collection
Message-ID:  <20031203142723.GB72102@droso.net>
In-Reply-To: <20031203135442.B82729@abigail.blackend.org>
References:  <20031203124353.GD82966@droso.net> <20031203135442.B82729@abigail.blackend.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On Wed, Dec 03, 2003 at 01:54:42PM +0100, Marc Fonvieille wrote:
> On Wed, Dec 03, 2003 at 01:43:53PM +0100, Erwin Lansing wrote:
> > Hi Doc!
> > 
> > As mentioned on -developers, I've taken it upon me to try and see if we,
> > the ports people, can create a document not much unlike the Release
> > Notes from our src brothers. Thoughts so far are that it should be some
> > kind of combination of /usr/src/UPDATING and relnotes, where both major
> > changes to major ports (ie. GNOME) can be announced to users and major
> > changes to ports infrastructure (ie. bsd.port.mk) can get more attention
> > of committers.
> > 
> > The first thing to decide would be which form this document should be
> > in. My first thought would be an article so we both have an online and
> > an offline version. One disadvantage of this would be that the offline
> > version would not be updating along with an update of the ports
> > collection via cvsup.
> >
> [...]
> 
> Release Notes live in src/, so it should be the same for your doc, i.e.
> in ports/, maybe in ports/Template or ports/Tools, or a specific directory.
> And something inside ports/ will prevent need of various repo access and
> could be updated via a cvsup, etc.
> 
Neat, I didn't know that. That should be one problem solved :)


-- 
                    _._     _,-'""`-._
Erwin Lansing      (,-.`._,'(       |\`-/|    erwin@lansing.dk
http://droso.org       `-.-' \ )-`( , o o)    erwin@FreeBSD.org
                    -bf-      `-    \`_`"'-

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/zfLLqy9aWxUlaZARAt/zAKD3i9ZagWNAKrCgeVe7Q7PBI8veuwCfVGGL
ZRKWZJTbw0HldUae6gblQp4=
=9+0W
-----END PGP SIGNATURE-----
help

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