From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1EtUy4-0003v6-GC for garchives@archives.gentoo.org; Mon, 02 Jan 2006 19:03:40 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k02J2Gck014081; Mon, 2 Jan 2006 19:02:16 GMT Received: from mail.twi-31o2.org (66-191-187-123.dhcp.gnvl.sc.charter.com [66.191.187.123]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k02IwvUm006879 for ; Mon, 2 Jan 2006 18:58:58 GMT Received: from localhost (localhost [127.0.0.1]) by mail.twi-31o2.org (Postfix) with ESMTP id 7E535248022 for ; Mon, 2 Jan 2006 13:49:39 -0500 (EST) Received: from mail.twi-31o2.org ([127.0.0.1]) by localhost (gravity.twi-31o2.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09099-04 for ; Mon, 2 Jan 2006 13:49:36 -0500 (EST) Received: from vertigo.twi-31o2.org (vertigo.twi-31o2.org [192.168.0.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.twi-31o2.org (Postfix) with ESMTP id 27003248021 for ; Mon, 2 Jan 2006 13:49:36 -0500 (EST) Subject: Re: [gentoo-dev] ChangeLogs and rsync time From: Chris Gianelloni To: gentoo-dev@lists.gentoo.org In-Reply-To: <43B961FC.10609@gentoo.org> References: <43B83D16.6060803@gentoo.org> <20060101225519.1f3bec72@snowdrop.home> <43B8F44D.4080806@gentoo.org> <43B9042B.2050802@quanteam.info> <20060102150025.GA6819@pluto.atHome> <43B956DC.9060402@gentoo.org> <20060102164729.GA31727@osgiliath.brixandersen.dk> <43B961FC.10609@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-jacxjWe58eVVSvt0wP56" Organization: Gentoo Linux Date: Mon, 02 Jan 2006 13:40:49 -0500 Message-Id: <1136227249.7131.1.camel@vertigo.twi-31o2.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 X-Virus-Scanned: amavisd-new at twi-31o2.org X-Archives-Salt: a8256c8b-1a45-42fe-a6d7-3371e5e10af4 X-Archives-Hash: 6aae32ce7a4fa538b3b8e86dc87eadb3 --=-jacxjWe58eVVSvt0wP56 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2006-01-02 at 11:25 -0600, Lance Albertson wrote:=20 > > I'm also for telling the users to rsync exclude the ChangeLogs if they > > don't want them instead of getting rid of them or crippling them. >=20 > I don't think that's really a solution. That's just a way to minimize > what they get. If you really want to look at a solution, you should > reduce whats actually in the changelog. All the changelogs are in CVS, > and if someone wanted to go look back at any changes, they can either > look at viewcvs or (hopefully soon), grab it via anoncvs. I bet you >80% > of things in the changelogs are for things that are in the attic. I say > we need a way to either have echangelog (or another script) to clean out > changelog entries for things that are in the attic (and make sense to > take out). Maybe another option would be to remove any 'version bump' > type entries that are old as well. OK. I keep seeing this argument about ChangeLog stuff for ebuilds in the Attic and I just think people might not be thinking it totally trough. For example, I made changes to the vmware-workstation ebuilds to force group membership a while back because of a security bug. However, there's been another security bug since, so those changes were made on ebuilds now in Attic, but the change is still valid in the current ebuilds. I don't see a problem with removing version bump and stabilization messages, but everything else should stay in the ChangeLog for as long as the package is still around. > I just don't see the point of keeping changelog entries for stuff that > isn't even viewable in the tree anymore. We have CVS, the record will be > there, lets use it. We can't cater to every user out there, but come up > with a solid solution that makes sense and still gives them some form of > ability to look back. Because as I stated before, there are many times where the ChangeLog entry for an older ebuild applies to the newer ones. This is especially true when ebuilds are simply copied for version bumps. Removing this information removes a lot of data. Forcing users/developers to use CVS makes it more of a hassle than the gains will give us. Again, I think this is another case of us doing things that aren't necessary rather than educating users. I wouldn't have a problem with seeing ChangeLog in a default RSYNC_EXCLUDES with a nice comment explaining how to get the ChangeLog files. This way we are removing the problem by default, educating users, and still not removing any data or options for our users and developers. --=20 Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux --=-jacxjWe58eVVSvt0wP56 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBDuXOxkT4lNIS36YERAgG9AJ9Eu3fggQ+Kc7NGjGRiY7sG+Ez+3wCfRNPo umdjLqMm8YFcmktWfutGR+I= =QK7r -----END PGP SIGNATURE----- --=-jacxjWe58eVVSvt0wP56-- -- gentoo-dev@gentoo.org mailing list