From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56 invoked by uid 1002); 12 Jul 2003 19:40:15 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 26739 invoked from network); 12 Jul 2003 19:40:15 -0000 From: Grant Goodyear To: Stewart Honsberger , gentoo-dev@gentoo.org In-Reply-To: <3F105B0D.8050200@gentoo.org> References: <3F105B0D.8050200@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-oakwMcYDUOqWOSmQiMfk" Message-Id: <1058038785.3216.32.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 12 Jul 2003 15:39:45 -0400 Subject: Re: [gentoo-dev] Portage, SLOT, functionality, documentation, ChangeLog X-Archives-Salt: 1642f31b-40b1-434e-bbe8-a55dd9efd719 X-Archives-Hash: 33c441ff39a43e87134fdeadea00cd58 --=-oakwMcYDUOqWOSmQiMfk Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > Portage has an abhorrent lack of documentation, I'd like to see that=20 > changed. Possibly > (especially) before a 1.4 release. I don't think there's a snowball's chance in Death Valley of that happening, just due to time restrictions. It's certainly true, though, that we do need to consolidate and improve the portage docs. > Also, and I can't stress this enough, a ChangeLog is *required*. When=20 > key functionality > is introduced, updated, removed, or significantly altered, it is=20 > imperative that users > and developers alike can be easily appraised of it in a common location. You'll find that the ChangeLog gets installed in /usr/share/doc/portage-x.y.z. Of course, it might be nice to know what's changed before you upgrade. The ChangeLog in sys-apps/portage incorrectly points people to viewcvs on cvs.g.o, although that's simple enough to fix. Slightly more difficult is the fact that gentoo-src is no longer linked to viewcvs. Since portage and rc scripts are developed there, having web access is really handy. Can we fix that? (Numerous cheers, by the way, for the prompt return of viewcvs. Thanks!!!) > A roadmap would also help a lot of people rest easy at night. Whether it=20 > is the case or > not, it seems as if major changes take place in Portage on a whim. If=20 > they are planned, > the general userbase has no foreknowledge of said plans and these=20 > changes come as > a complete surprise when finally marked stable in the tree (if people=20 > even know they > exist, due to the aforementioned lack of documentation). *Grin* The roadmap _used_ to be a "TODO" block in portage.py. Having a somewhat more formal roadmap would be a nice idea, and I don't know if one exists or not, although I'd be rather surprised if one didn't. Best, g2boojum --=20 Grant Goodyear --=-oakwMcYDUOqWOSmQiMfk Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/EGQBptxxUuD2W3YRAsHEAJ9CHONyjLV2uLeHbSPDRn1vmZbPcACfX1fn iC5FYr1sRT5F+EtxTnw7ENY= =WRE7 -----END PGP SIGNATURE----- --=-oakwMcYDUOqWOSmQiMfk--