From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Our package names should not include "github-com" Date: Fri, 13 Oct 2017 17:41:53 +0000 Message-ID: <20171013174153.olarqmf4tjimp7ii@abyayala> References: <20171013014334.17601.30718@vcs0.savannah.gnu.org> <20171013014344.D813E20338@vcs0.savannah.gnu.org> <87lgkfhszj.fsf_-_@netris.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gwurmkazbhzd3643" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34888) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e33yT-0000S5-9h for guix-devel@gnu.org; Fri, 13 Oct 2017 13:42:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e33yQ-0001ZQ-5Z for guix-devel@gnu.org; Fri, 13 Oct 2017 13:42:17 -0400 Received: from aibo.runbox.com ([91.220.196.211]:43920) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e33yP-0001Yt-U6 for guix-devel@gnu.org; Fri, 13 Oct 2017 13:42:14 -0400 Content-Disposition: inline In-Reply-To: <87lgkfhszj.fsf_-_@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver Cc: guix-devel@gnu.org --gwurmkazbhzd3643 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mark H Weaver transcribed 0.9K bytes: > Hi Leo, >=20 > leo@famulari.name (Leo Famulari) writes: >=20 > > lfam pushed a commit to branch master > > in repository guix. > > > > commit 478ebb31a96955fc03fcea55a4432976ddb49319 > > Author: Leo Famulari > > Date: Wed Oct 11 20:22:32 2017 -0400 > > > > gnu: Add go-github-com-templexxx-reedsolomon. >=20 > On this, and a great many other packages, you've included "github-com-" > in the package names. I think this is a very bad idea. For one thing, > we should not advertise, promote, or enhance the lock-in of GitHub, and > this policy does all three. Sometimes a maintainer decides to change > their hosting arrangements. When they do so, we should simply be able > to update some URLs in one package definition. We should not have to do > a global find/replace on the package name and alert our users to update > their profiles and OS definitions. That contributes to lock-in. >=20 > What do you think? >=20 > Mark I think Leo just followed the upstream conventions here, where it is named after the path the go module ends in. If we decide not to name the package like this, we might break expectations. So when we break expectations, what are the alternative naming schemes we could pick for go packages that'll still make sense to people using Go? --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://dist.ng0.infotropique.org/dist/keys/ https://www.infotropique.org https://ng0.infotropique.org --gwurmkazbhzd3643 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlng+uAACgkQ4i+bv+40 hYhnUQ/9GcaYBxhQWXAygu2uZgHOzkmFbIIl3Wqs1ueX1JGUyda4vwyZmFASFixo lrXH6Sxt7DoyFNp+kxiqDlRzWf6s4yn4hOW44F1exgU+mKf+rZRO+vjcbcW4BIuY gomQ3i9DMTk15olX6n9OY70eKpVh9VHhHGPczzk/zXuCC6fBvB/I3085TOxwWGU1 jaFPb3PGnqc7JFkS9pLLDtXTkroUFIjKjlULvcjQ0UZ28I+zyVTyM1WmsYy8SoGg aJ89L7jWaSEjkeiJSieM/urHyFYBukO/4LVdP5cPuB4nz588oPamE491aq001ueM y/V5HSE0gQfu9a0uQhJyL/ktvjrG2f2Ynd1vf3WrQWaTgfjDM+TUvayxFEbf7h98 ypKSZXU46BY8C+dcPIPBXsHmjB8fxiP2YNNixc6WiX0IRYy2RFAgdDkB3R+skCRi Cb8AnwKvhzwg4d6NBCAt/INXB4cLbyQ78v5IKPyxSFcJAMFEXcYYDzNYI/Qha7D6 Iul03eDKgZk3IRzlV5YhjlUikZauG3J5rZxzaBcpUleKrVdjs3B5niqQRLQNSHa4 c4NxANi4xzJYraZezDTdqC/+SWlcog2OeLL+TJOIGzNst3t1lcDxEJ7RnhLsJTnL xmXzsg3UhCARz7sMv+Ra0fy4w48jYg69DW59wK3xDjjJvivz97o= =ejSa -----END PGP SIGNATURE----- --gwurmkazbhzd3643--