From: david.larsson@selfhosted.xyz
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: guile-bash updated source url
Date: Sun, 5 May 2019 13:07:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.21.9999.1905051305510.11664@localhost> (raw)
In-Reply-To: <87imurbq18.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2980 bytes --]
Hi Andreas & Ludo,
On Fri, 3 May 2019, Ludovic Courtès wrote:
> Hello David,
>
> david.larsson@selfhosted.xyz skribis:
>
>> This is my first contribution to guix and it's just a minor fix for
>> the guile-bash package which had an outdated source url. I was able to
>> retrieve the same revision of the package via the software-heritage
>> project's website and upload it to gitlab. Then I installed it
>> successfully via guix package -f my-guile-bash.scm using the gitlab
>> url, then copied it to the existing guile-xyz.scm in gnu/packages.
>
> [...]
>
>> --- a/gnu/packages/guile-xyz.scm
>> +++ b/gnu/packages/guile-xyz.scm
>> @@ -294,23 +294,21 @@ dictionary and suggesting spelling corrections.")
>> (license license:gpl3+)))
>>
>> (define-public guile-bash
>> - ;; This project is currently retired. It was initially announced here:
>> - ;; <https://lists.gnu.org/archive/html/guile-user/2015-02/msg00003.html>.
>> - (let ((commit "1eabc563ca5692b3e08d84f1f0e6fd2283284469")
>> + (let ((commit "49099fe6a592aa3b8001e826b939869fe5811785")
>> (revision "0"))
>
> Why is the commit different? Looks like it’s more than just a mirror.
>
> If you made changes on top of the original code, that’s actually great.
> However, I’d prefer to first see a patch that simply changes the URL,
> not the commit and hash, and later updates to a different revision.
>
> Does that make sense?
>
I made a commit since I was unable figure out how to create a
git-mirror from the Software Heritage website but was able to retrieve
the correct commit as a tarball. Then I guix init'ed the folder, and
made a commit in order to push it to gitlab.
> Andreas Enge <andreas@enge.fr> skribis:
>
>> should the package not be retrieved automatically from Software Heritage
>> with the newest Guix API? And apart from that, will it be desirable to keep
>> around an unmaintained software for which the source has disappeared?
I don't know if the newest Guix API would fix it, but I haven't been
able to install guile-bash from source so far using e.g. guix
challenge. I can't really answer your second question, but I will
personally use the package and thought it would be nice to be able to
retrieve it from a standard Guix install and that it can be built and
challenged. Previously I had to add additional --substitute-url's to
guix install it.
>
> I think David is in fact suggesting that they may well be maintaining
> it, which is good news IMO. :-)
I wish that was the case - maybe in the future, I am slowly learning
Guile at the moment :-)
Currently, I can at most support the package definition and change the
url if someone notifies me they want to start actively maintaining it.
So I don't know if you think the patch should be rejected or not.. maybe
the comment about the project being retired should remain, if so I can
resubmit a patch.
Thanks for your comments,
// David L
next prev parent reply other threads:[~2019-05-05 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 8:28 guile-bash updated source url david.larsson
2019-05-01 10:11 ` Andreas Enge
2019-05-03 13:56 ` Ludovic Courtès
2019-05-05 11:07 ` david.larsson [this message]
2019-05-05 22:58 ` Mark H Weaver
2019-05-08 4:25 ` Mark H Weaver
2019-05-11 16:08 ` david.larsson
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=alpine.LNX.2.21.9999.1905051305510.11664@localhost \
--to=david.larsson@selfhosted.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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 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).