From: ng0 <ng0@infotropique.org>
To: Mark H Weaver <mhw@netris.org>, Leo Famulari <leo@famulari.name>,
guix-devel@gnu.org
Subject: Re: Our package names should not include "github-com"
Date: Fri, 13 Oct 2017 17:44:40 +0000 [thread overview]
Message-ID: <20171013174440.obwk6wdpwllagiz4@abyayala> (raw)
In-Reply-To: <20171013174153.olarqmf4tjimp7ii@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]
ng0 transcribed 2.5K bytes:
> Mark H Weaver transcribed 0.9K bytes:
> > Hi Leo,
> >
> > leo@famulari.name (Leo Famulari) writes:
> >
> > > lfam pushed a commit to branch master
> > > in repository guix.
> > >
> > > commit 478ebb31a96955fc03fcea55a4432976ddb49319
> > > Author: Leo Famulari <leo@famulari.name>
> > > Date: Wed Oct 11 20:22:32 2017 -0400
> > >
> > > gnu: Add go-github-com-templexxx-reedsolomon.
> >
> > 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.
> >
> > What do you think?
> >
> > 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?
One idea could be:
go-templexxx-reedsolomon
so just remove the hoster from the package name.
I'm not using Go, so I don't know if this will make any sense
or cause potential namespace issues.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://dist.ng0.infotropique.org/dist/keys/
https://www.infotropique.org https://ng0.infotropique.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-13 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171013014334.17601.30718@vcs0.savannah.gnu.org>
[not found] ` <20171013014344.D813E20338@vcs0.savannah.gnu.org>
2017-10-13 17:12 ` Our package names should not include "github-com" Mark H Weaver
2017-10-13 17:41 ` ng0
2017-10-13 17:44 ` ng0 [this message]
2017-10-13 20:24 ` Leo Famulari
2017-10-14 1:05 ` Mark H Weaver
2017-10-16 0:41 ` Maxim Cournoyer
2017-10-16 21:38 ` Leo Famulari
2017-10-17 10:44 ` Leo Famulari
2017-10-18 2:09 ` Maxim Cournoyer
2017-10-16 13:05 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171013174440.obwk6wdpwllagiz4@abyayala \
--to=ng0@infotropique.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.