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 1Rwgrh-0007ip-4v for garchives@archives.gentoo.org; Sun, 12 Feb 2012 21:21:45 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CAA72E0879; Sun, 12 Feb 2012 21:21:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id EBDE3E0874 for ; Sun, 12 Feb 2012 21:21:07 +0000 (UTC) Received: from pomiocik.lan (unknown [87.204.190.177]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 0ED5F1B4014; Sun, 12 Feb 2012 21:21:05 +0000 (UTC) Date: Sun, 12 Feb 2012 22:22:58 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: tetromino@gentoo.org Subject: Re: [gentoo-dev] RFC: Application name in metadata.xml Message-ID: <20120212222258.3cce66e3@pomiocik.lan> In-Reply-To: <1329081282.446.9.camel@rook> References: <4F37DE18.7080904@gentoo.org> <20280.5374.577507.960890@a1i15.kph.uni-mainz.de> <1329081282.446.9.camel@rook> Organization: Gentoo X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-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: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/zIFxBWNC3KzHPXcCAO5MLmN"; protocol="application/pgp-signature" X-Archives-Salt: df8fdbaf-c781-497c-ad44-aee98b7aefc8 X-Archives-Hash: 159b95aaa11eacbf19aa805f241c63b5 --Sig_/zIFxBWNC3KzHPXcCAO5MLmN Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, 12 Feb 2012 16:14:42 -0500 Alexandre Rostovtsev wrote: > On Sun, 2012-02-12 at 20:37 +0100, Ulrich Mueller wrote: > > >>>>> On Sun, 12 Feb 2012, Pawe=C5=82 Hajdan, wrote: > >=20 > > > On 2/11/12 2:00 PM, Fabio Erculiani wrote: > > >> Other distros associate a more user-friendly package name > > >> (application name) to packages. > > >> Say, they bind libreoffice-writer to "LibreOffice Writer" in > > >> package metadata. > >=20 > > [Replying to a random message in this thread.] > >=20 > > Why do you think that writing the package name in mixed case and > > with embedded white space would be more "user friendly"? >=20 > because-removing-all-upper-case-spaces-and-punctuation-from-a-string > makes it less readable to a non-programmer. >=20 > > >> How about expanding metadata.xml (adding to its .dtd) to also > > >> support this? > >=20 > > I still don't see what this would buy us. So far we have a unique > > identifier (namely ${CATEGORY}/${PN}) for our packages. Introducing > > another name will water this down and cause confusion for users, in > > the first place. > >=20 > > So, can you point out what are the advantages of your proposal? > > Are they large enough to outweigh the confusion arising? >=20 > Users know a package's "natural name", not the occasionally cryptic > ebuild name, and certainly not the category. If I want to install a > game called "Neverwinter Nights", it may not be immediately apparent > to me that I should emerge something called "games-rpg/nwn". >=20 > Adding the natural name to metadata would allow users to more easily > find the packages they need via packages.gentoo.org and tools like > eix. And make it less possible that users will actually report a bug and suggest changing the package name to a less ambiguous one. And AFAICS there's no 'nwn' in SRC_URI so it's just pointless to abbreviate the name like that in our ebuild name. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/zIFxBWNC3KzHPXcCAO5MLmN Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iJwEAQEIAAYFAk84LbcACgkQfXuS5UK5QB1pjQP/dgpKw6OIr1oYOa8eW6G6+QcY gFCckia+i2omDfnu3gO4iWiPvPg5M1YUBxQOyXoE8nbTyow2vbNhPNESbw20cQ8/ 1PxvOrjI5/o3fzWc2YsHDwd9W0d1ua+T6B+CaYzWwYO33ETWjDIRYJIkvF+m/9DF 7duBDwofn9bf2ur5KNc= =O9ua -----END PGP SIGNATURE----- --Sig_/zIFxBWNC3KzHPXcCAO5MLmN--