all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Leo Famulari <leo@famulari.name>
Cc: rekado@elephly.net, 34079@debbugs.gnu.org
Subject: [bug#34079] [PATCH] sshfs rename (Was: Re: Proposal: rename sshfs-fuse -> sshfs)
Date: Mon, 14 Jan 2019 21:12:52 +0100	[thread overview]
Message-ID: <87y37nov5n.fsf_-_@riseup.net> (raw)
In-Reply-To: <20181114172526.GA2408@jasmine.lan> (Leo Famulari's message of "Wed, 14 Nov 2018 12:25:26 -0500")

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

Leo Famulari <leo@famulari.name> writes:

> On Wed, Nov 14, 2018 at 12:41:59PM +0100, Ricardo Wurmus wrote:
>> I have no objections to renaming the package, though you’ll need to keep
>> a definition for “sshfs-fuse” to indicate to users that the package has
>> been renamed.
>
> Right. See the definition of 'letsencrypt' in (gnu packages tls) for an
> example of this.

Done.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-Rename-sshfs-fuse-to-sshfs.patch --]
[-- Type: text/x-patch, Size: 1272 bytes --]

From 86536694d40eb42e746b55cac5caa98e28946ed1 Mon Sep 17 00:00:00 2001
From: swedebugia <swedebugia@riseup.net>
Date: Mon, 14 Jan 2019 21:03:20 +0100
Subject: [PATCH] gnu: Rename sshfs-fuse to sshfs.

* gnu/packages/linux.scm
  (sshfs-fuse): Mark as superseeded.
  (sshfs): New variable.
---
 gnu/packages/linux.scm | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 4fb85f2f3..4b70694d2 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -1810,9 +1810,9 @@ UnionFS-FUSE additionally supports copy-on-write.")
                #t))))))
     (inputs `(("fuse" ,fuse-static)))))
 
-(define-public sshfs-fuse
+(define-public sshfs
   (package
-    (name "sshfs-fuse")
+    (name "sshfs")
     (version "2.10")
     (source (origin
               (method url-fetch)
@@ -1837,6 +1837,11 @@ up: on the server side there's nothing to do; on the client side mounting the
 file system is as easy as logging into the server with an SSH client.")
     (license license:gpl2+)))
 
+(define-public sshfs-fuse
+  (package (inherit sshfs)
+    (name "sshfs-fuse")
+    (properties `((superseded . ,sshfs)))))
+
 (define-public archivemount
   (package
     (name "archivemount")
-- 
2.19.2


  reply	other threads:[~2019-01-14 20:22 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
2018-11-14 11:41   ` Ricardo Wurmus
2018-11-14 17:25     ` Leo Famulari
2019-01-14 20:12       ` swedebugia [this message]
2019-01-15 15:49         ` bug#34079: [PATCH] sshfs rename (Was: Re: Proposal: rename sshfs-fuse -> sshfs) 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=87y37nov5n.fsf_-_@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=34079@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=rekado@elephly.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.