all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Proposal: rename sshfs-fuse -> sshfs
Date: Wed, 14 Nov 2018 12:47:02 +0300	[thread overview]
Message-ID: <87o9as9ejt.fsf@gmail.com> (raw)
In-Reply-To: <ae361e6d-c106-39c9-de88-1311dda48721@riseup.net> (swedebugia's message of "Tue, 13 Nov 2018 02:22:07 +0100")

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

Hello,

swedebugia <swedebugia@riseup.net> writes:

> Reasons:
> * shorter is better.

Not always, e.g. as you see we have a policy to prefix package names
like font-dejavu and emacs-guix, but I don't see this in ‘fuse’ case:
--8<---------------cut here---------------start------------->8---
$ guix package -A fuse | awk '{ print $1 }'
enblend-enfuse
fuse
fuse-exfat
libconfuse
python-defusedxml
python-fusepy
python-llfuse
python-llfuse
python2-defusedxml
python2-fusepy
python2-llfuse
sshfs-fuse
unionfs-fuse
unionfs-fuse-static
--8<---------------cut here---------------end--------------->8---

> * the project it self names it sshfs.

It was an “issue” for me to install sshfs by naive typing
‘guix package -i sshfs’ :-)

> * there are no other sshfs implementations to my knowledge

Agree.

Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-11-14  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  1:22 Proposal: rename sshfs-fuse -> sshfs swedebugia
2018-11-14  9:47 ` Oleg Pykhalov [this message]
2018-11-14 11:41   ` Ricardo Wurmus
2018-11-14 17:25     ` Leo Famulari
2019-01-14 20:12       ` [bug#34079] [PATCH] sshfs rename (Was: Re: Proposal: rename sshfs-fuse -> sshfs) swedebugia
2019-01-15 15:49         ` bug#34079: " Leo Famulari

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=87o9as9ejt.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.net \
    /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.