unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 36851@debbugs.gnu.org
Subject: [bug#36851] [PATCH] Add rclone-browser
Date: Thu, 05 Sep 2019 10:44:46 +0200	[thread overview]
Message-ID: <87y2z3gmip.fsf@gnu.org> (raw)
In-Reply-To: <87a7bkoxjs.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 04 Sep 2019 18:07:03 +0200")

Hello,

Nicolas Goaziou <mail@nicolasgoaziou.fr> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>>> * gnu/packages/sync.scm (rclone-browser): New variable.
>>
>> LGTM!
>
> Thank you for the review.
>
>> Note that, as noted in ‘HACKING’, it’s the kind of change that you can
>> push quickly if you don’t get any feedback.
>
> Well, this one had a question: should I also propagate `rclone'? Since
> I wasn't sure about it, I didn't applied the patch.

Oh indeed, sorry.  The general rule is that propagation should be
avoided as much as possible.  Is there a way you could ‘substitute*’ the
reference to ‘rclone’ in ‘rclone-browser’?

> Also, there is an issue : according to
> <https://martins.ninja/RcloneBrowser/>, the project is no longer active
> nor maintained.
>
> Should we bother anymore and package it?

It depends.  In general we’d rather not package unmaintained software.
However, there are cases where people do rely on unmaintained software,
for better or worse.

If you think that there’s no other options that fits the bill for you as
a user, maybe it’s a sign that we should package it, possibly removing
it later down the road.  Otherwise, perhaps we shouldn’t bother.

WDYT?

Thanks,
Ludo’.

      reply	other threads:[~2019-09-05  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30  8:17 [bug#36851] [PATCH] Add rclone-browser Nicolas Goaziou
2019-09-04 12:26 ` Ludovic Courtès
2019-09-04 16:07   ` Nicolas Goaziou
2019-09-05  8:44     ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2z3gmip.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36851@debbugs.gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).