From: Federico Beffa <beffa@ieee.org>
To: Alex Kost <alezost@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Patches to add emacs-rfcview and emacs-ffap-rfc-space
Date: Thu, 14 Apr 2016 18:59:39 +0200 [thread overview]
Message-ID: <CAKrPhPN_B_rwmuffH53_mk7nJJk2RznX1rQL+ku5+ovGh6hrYw@mail.gmail.com> (raw)
In-Reply-To: <8737qryzgp.fsf@gmail.com>
On Tue, Apr 12, 2016 at 10:59 AM, Alex Kost <alezost@gmail.com> wrote:
> Alex Kost (2016-04-05 12:29 +0300) wrote:
>
>> Chris Marusich (2016-04-04 03:58 +0300) wrote:
>>
>>> Hi,
>>>
>>> The attached patches add some useful modules for reading RFCs (and STDs)
>>> in Emacs.
>>
>> Overall the patches look good to me, thanks! But there is a problem
>> with both packages: the URL of the origin does not point to a versioned
>> file, so when the author will touch the source, the hash will be changed
>> and our package will not work anymore. I suppose there are no mirrors
>> where we can fetch the "constant" source code, so we probably have to
>> live with this, but it is a potential problem-maker.
>
> Ping for the other reviewers. I don't know what to do with these
> packages: on one hand they are unreliable because their hashes may
> change any time. But OTOH we already have the same potential problems
> with 'emacs-mit-scheme-doc' and 'emacs-constants' packages.
>
> I personally wouldn't like to include such packages in Guix at all. I
> think the only hope with them is that they are dead, so their hashes
> will not be changed. Federico, did you have this problem in mind when
> you packaged them?
Of course I did and I agree it is annoying.
'emacs-constants' has not been changed in a long time because it is
kind of "done". I've recently sent a patch to the author and took the
occasion to mention to him that it would help us to have versioned
releases. He accepted the patch, but I think he is not into archiving
old versions. So probably this package will soon break, but it will be
a matter of fixing the hash (and maybe again in a few years).
In any case, from my point of view, proposing to drop packages is not
very constructive. A more helpful approach would be to find a place
where we could archive specific versions of packages with this kind of
problem. I know that people here do not particularly like GitHub, but
possibly a similar place/service could do.
Regards,
Fede
next prev parent reply other threads:[~2016-04-14 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 0:58 Patches to add emacs-rfcview and emacs-ffap-rfc-space Chris Marusich
2016-04-05 9:29 ` Alex Kost
2016-04-12 8:59 ` Alex Kost
2016-04-14 16:59 ` Federico Beffa [this message]
2016-04-15 8:36 ` Alex Kost
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=CAKrPhPN_B_rwmuffH53_mk7nJJk2RznX1rQL+ku5+ovGh6hrYw@mail.gmail.com \
--to=beffa@ieee.org \
--cc=alezost@gmail.com \
--cc=guix-devel@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).