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 1EtB8J-0001X0-3i for garchives@archives.gentoo.org; Sun, 01 Jan 2006 21:52:55 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k01LphcM015544; Sun, 1 Jan 2006 21:51:43 GMT Received: from hermes.orakel.ods.org (dsl67-66.fastxdsl.nl [62.251.66.67]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k01LmLXB003514 for ; Sun, 1 Jan 2006 21:48:21 GMT Received: from aphrodite.orakel.ods.org ([172.17.2.15]) by hermes.orakel.ods.org with esmtp (Exim 4.54) id 1EtB3s-0004D9-7V for gentoo-dev@lists.gentoo.org; Sun, 01 Jan 2006 22:48:21 +0100 Received: by aphrodite.orakel.ods.org (Postfix, from userid 501) id F3D7A1CA9F1; Sun, 1 Jan 2006 22:48:18 +0100 (CET) Date: Sun, 1 Jan 2006 22:48:18 +0100 From: Grobian To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] ChangeLogs and rsync time Message-ID: <20060101214818.GB17018@gentoo.org> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <43B83D16.6060803@gentoo.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 Content-Type: text/plain; charset=utf8 Content-Disposition: inline In-Reply-To: <43B83D16.6060803@gentoo.org> User-Agent: Mutt/ng-r655 (Darwin 8.3.0, VIM - Vi IMproved 6.2) Organization: Gentoo Foundation, Inc. X-Content-Scanned: by hermes.orakel.ods.org (Exim Exiscan) using SpamAssassin and ClamAV X-Archives-Salt: af71cc7f-929a-46ac-bc6e-c699e0aaf453 X-Archives-Hash: ca91884a32970be605637d13fbab907d On 01-01-2006 21:35:34 +0100, Francesco Riosa wrote with possible deletions: > The information contained in the ChangeLogs is essential, and it must be > kept, but, force the users to download all that data it's not optimal. > > That said I can see only two ways to reduce the ChangeLog files (a > centralized one is obviously not viable) > > 1) bzip2 them in some way. > 2) "rotate" Changelogs, keeping only the last changes, until a size or 3) remove entries for non-existing ebuilds This may, or may not be a good idea, but it is founded on the following observation: currently old or redundant ebuilds are removed from the tree. Once that happens, they don't show up in the rsync tree and are only available through the (centralised) CVS Attic. One can argue that Changelog entries for non-existing ebuilds are not of any use, since the files they refer to aren't present. This method would clean up the Changelog entries, in the same way ebuilds are removed, and CVS keeps the history around. 4) compress Changelog entries where possible Often, a package is marked testing or stable on request via a bug. This usually results in having as much as new Changelog entries as there are arch teams involved. These kind of entries, that all more or less report 'Marked arch' could be merged into one, given that the information itself is Changelog-worthy anyway. (This is arguable IMHO.) This method may involve a lot of fuzzy matching to perform it automatically, with its related risks. The win for the large Changelog files is probably minimal. -- Fabian Groffen -- gentoo-dev@gentoo.org mailing list