From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L74eJ-0007BQ-Q7 for garchives@archives.gentoo.org; Mon, 01 Dec 2008 09:01:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B9844E0266; Mon, 1 Dec 2008 09:00:57 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 73F7AE0266 for ; Mon, 1 Dec 2008 09:00:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id EB8DF64535 for ; Mon, 1 Dec 2008 09:00:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -3.08 X-Spam-Level: X-Spam-Status: No, score=-3.08 required=5.5 tests=[AWL=0.519, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mxehm0sDjzGg for ; Mon, 1 Dec 2008 09:00:50 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 444AB645B1 for ; Mon, 1 Dec 2008 09:00:49 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L74e2-0004sr-Sd for gentoo-dev@gentoo.org; Mon, 01 Dec 2008 09:00:42 +0000 Received: from ppp-122-238.21-151.libero.it ([151.21.238.122]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Dec 2008 09:00:42 +0000 Received: from flameeyes by ppp-122-238.21-151.libero.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Dec 2008 09:00:42 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: flameeyes@gmail.com (Diego 'Flameeyes' =?utf-8?Q?Petten=C3=B2?=) Subject: [gentoo-dev] Re: [RFC] Moving HOMEPAGE out of ebuilds for the future Date: Mon, 01 Dec 2008 10:00:33 +0100 Message-ID: References: <49329690.7000409@gentoo.org> <1228053002.5981.12.camel@homer.ob.libexec.de> <1228057415.25651.105.camel@localhost> <4932AC9D.2000401@gentoo.org> <1228064022.25651.151.camel@localhost> 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: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ppp-122-238.21-151.libero.it User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:EhrHpsCfJDfgryhvfTn+coNZ8Co= Sender: news X-Archives-Salt: 1629cc63-34fd-4b1b-a74c-4bffa68dc747 X-Archives-Hash: c1ff60131903ae0822638923ed2238d4 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable "Alec Warner" writes: > That being said I still don't see the usefulness here. > > You seem to think that using the existing APIs for this data is wrong, > and I think the opposite, so I guess we will agree to disagree on this > matter. Yeah I still think that there is no point in requiring using of a specific API when the same data can easily be available in a format that is more or less parsable with ease in any modern (and non) programming language. Beside, I find expanding the HOMEPAGE syntax to allow more than one link a bit ... overkill, if the same thing can be achieved in metadata.xml... >> Beside, if you really want to go down that road you should be counting >> that beside ReiserFS with tail, I don't remember any other Linux FS that >> has block smaller than 512bytes, which means that each file in metadata >> cache is taking up much more than just its size in characters. >> >> All your math is thus wrong. > > As was pointed out on IRC, UTF8 characters are not a fixed size, > making my math even more wrong ;) If we consider HOMEPAGE, the assumption that characters are fixed size to 1 byte is good enough; URLs are usually encoded in pure ascii character space for compatibility; while IDN would break that assumption, we can't even assume that IDN is always available and so on. For description maybe it's different because there is space there for UTF-8 characters, but that's going to bring us even farthest than the point. =2D-=20 Diego "Flameeyes" Petten=C3=B2 http://blog.flameeyes.eu/ --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkzp7EACgkQe2h1+2mHVWOI5QCcC1tRRcyF8LtdqLLkR7UryGf4 U8YAnjESrXInQBC9DzO8Shrqh8IVjbrE =HdCD -----END PGP SIGNATURE----- --=-=-=--