From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25356 invoked from network); 30 Jul 2004 07:22:31 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 30 Jul 2004 07:22:31 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BqRip-0006Zu-7x for arch-gentoo-dev@lists.gentoo.org; Fri, 30 Jul 2004 07:22:31 +0000 Received: (qmail 19653 invoked by uid 89); 30 Jul 2004 07:22:30 +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 1340 invoked from network); 30 Jul 2004 07:22:30 +0000 Date: Fri, 30 Jul 2004 00:00:01 -0700 From: "Robin H. Johnson" In-reply-to: <20040730050727.7b6f82ee@snowdrop.home> To: Gentoo Developers Mail-followup-to: Gentoo Developers Message-id: <20040730070001.GA27235@curie-int.orbis-terrarum.net> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=Qxx1br4bt0+wmkIi Content-disposition: inline User-Agent: Mutt/1.5.6i References: <1091094759.6176.23.camel@6-allhosts> <200407291015.20390.vapier@gentoo.org> <410955B0.1030301@gossamer-threads.com> <20040730031549.GA25543@ols-dell.iic.hokudai.ac.jp> <20040730042229.49ed034a@snowdrop.home> <20040730050727.7b6f82ee@snowdrop.home> Subject: Re: [gentoo-dev] Upcoming repoman check will fail on large files in the tree X-Archives-Salt: 2fd06e3d-411e-485b-8fbb-9f4833aec523 X-Archives-Hash: 18c7a1f9c7b4f36f4ab7f81782ebb167 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 30, 2004 at 05:07:27AM +0100, Ciaran McCreesh wrote: > On Fri, 30 Jul 2004 04:22:29 +0100 Ciaran McCreesh > wrote: > | On Fri, 30 Jul 2004 12:15:49 +0900 Georgi Georgiev > | wrote: > | | What about not allowing binary files at all? > |=20 > | That'd break ChangeLog. No it won't. > Ok, since I've been asked about this several times on IRC... Some people > have names which include non-[A-Za-z] characters. UTF8 !=3D binary. UTF8 is fine, it's specifically designed to co-exist with ASCII/ISO-8559-1. As such, CVS handles UTF8 perfectly well (UTF16 is a different matter). I'm in favour of removing all properly binary files from CVS, to get the checkout size down. Brian's earlier list of files over 20k comprises more than 9Mb of files, and that's a not even a complete list. Could we please consider removing sys-apps/portage/files/portage-rescue* =66rom the tree? These files are there, and comprise relatively large chunk of space. portage-rescue-2.0.44-ppc.tbz2 portage-rescue-2.0.48-r1-sparc64.tbz2 portage-rescue-2.0.49-r3-alpha.tbz2 portage-rescue-2.0.48-r1-sparc.tbz2 portage-rescue-2.0.49-r15-amd64.tbz2 The x86 portage rescue has already gone, and the others should join it. Leaving an README.RESCUE would be prudent. > Incidentally, when are we going to officially standardise on UTF-8 for > ChangeLog and ebuilds? There is absolutely nothing I'm aware of stopping you from using UTF already in ChangeLogs and ebuilds, barring some common sense limitations, like bash not accepting non-ASCII for the names of variables and functions. --=20 Robin Hugh Johnson E-Mail : robbat2@orbis-terrarum.net Home Page : http://www.orbis-terrarum.net/?l=3Dpeople.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Robbat2 @ Orbis-Terrarum Networks iD8DBQFBCfHxsnuUTjSIToURAmHkAJ0ayrM3/5g7cqTuz3qH9hkXDFgrFACgqAe5 Q76+GV+n5bcxD6Q3YX5rVIU= =V0H3 -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--