From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RJ97Q-00029V-2l for garchives@archives.gentoo.org; Wed, 26 Oct 2011 19:26:33 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D782E21C077; Wed, 26 Oct 2011 19:26:22 +0000 (UTC) Received: from mailgate.internet.lu (mailgate.internet.lu [195.218.0.131]) by pigeon.gentoo.org (Postfix) with SMTP id 6A87B21C060 for ; Wed, 26 Oct 2011 19:25:56 +0000 (UTC) Received: from silis.lu (mail.internet.lu [195.218.24.10]) by mailgate.internet.lu (Postfix) with SMTP id 1E59F9C0182 for ; Wed, 26 Oct 2011 21:25:55 +0200 (CEST) Received: from 158.64.145.50 by 195.218.24.10 INC_SMTP_SERVER 2.57; Wed, 26 Oct 2011 21:25:55 +0200 Received: from neptune.home (unknown [IPv6:2001:960:7ab:0:ad8c:4806:e214:ff13]) by smtp.home (Postfix) with ESMTP id 65F7F144C04 for ; Wed, 26 Oct 2011 21:25:54 +0200 (CEST) Date: Wed, 26 Oct 2011 21:24:49 +0200 From: Bruno To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [Council] ChangeLog generation within Gentoo Message-ID: <20111026212449.4471e2c1@neptune.home> In-Reply-To: <1319652453.5300.10.camel@belkin4> References: <20111026170212.GD843@gentoo.org> <20111026193356.058efef7@neptune.home> <1319652453.5300.10.camel@belkin4> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: aefcc614ed48625815d4ecbf44740342 On Wed, 26 October 2011 Pacho Ramos wrote: > El mi=C3=A9, 26-10-2011 a las 19:33 +0200, Bruno escribi=C3=B3: > > On Wed, 26 October 2011 Fabian Groffen wrote: > > > However, this also allows to do all kinds of other actions to the > > > ChangeLog file, without actually adding an entry for the current chan= ge > > > being committed, as we've already seen in practice. > > > The Council would like to remind developers that it is still a > > > requirement that all actions are documented in the ChangeLog and that= it > > > is hence the responsibility of the committing developer to make sure > > > this requirement is met. > >=20 > > Is there some guideline about old entries in the ChangeLog? > >=20 > > Over the past months ChangeLogs represent a big part of the tree, some > > of them being pretty big and going back many changes (hundreds of them) > > and years (even for actively maintained ebuilds). > >=20 > > In order to not bloat the tree I would like to see old entries purged > > when there are more than 25-50 of them, especially if they refer to > > ebuilds gone since more than 3-6 months. > > Someone in need for long gone ebuild would have to look at VCS anyhow, = so > > looking at ChangeLog/history over there would seem logical. > >=20 > > On a compressed tree (squashfs) dropping all ChangeLogs reduces size fr= om > > ~55MiB to around 35MiB which is quite a lot! >=20 > Personally, I want to have full ChangeLog easily accessible, I remember > to need to look for really old entries when becoming a new maintainer > for an old package previously maintained by others. That seems fair, though I guess old ebuilds are needed as well in that case so the not-trimmed ChangeLog probably rather should be a feature of VCS GUI that would take all the changes to ChangeLog and assemble all the additions ignoring the removed lines, possibly connecting that to the history of the individual ebuilds. > What I don't know is the reasons for not compressing ChangeLogs by > default (well, I don't have a compressed tree, this probably won't be a > gain for people using it) Compressing the ChangeLogs in the tree would not help rsync as the beginning of the file changes and thus the compressed binary result is all but a stre= am to which data got appended. Bruno