From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34865@debbugs.gnu.org, Brian Leung <bkleung89@gmail.com>
Subject: [bug#34865] [PATCH] Add emacs-zones.
Date: Tue, 26 Mar 2019 11:55:33 +0100 [thread overview]
Message-ID: <87tvfp52hm.fsf@elephly.net> (raw)
In-Reply-To: <87va06ht4f.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Oleg,
>
> Oleg Pykhalov <go.wigust@gmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>> […]
>>
>>>> Could we use emacs-zones from Elpa? See
>>>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>>>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>>>
>>> My understanding is that ELPA and MELPA tarballs are not necessarily
>>> persistent and immutable, and that we generally prefer referring
>>> directly to the upstream repo.
>>
>> Ouch, I thought ELPA is persistent. That's a significant argument to
>> not use ELPA for our purposes :-( .
I only know that MELPA isn’t immutable. I assumed that ELPA is fine.
>> We preferred ELPA over GitHub's Git repositories in emacs-xys.scm
>> (emacs.scm in past), didn't we?
>
> Hmmm, not sure, Ricardo, what’s the story? :-)
I don’t think we did. I can’t think of even one case where we switched
from git-fetch from GitHub to url-fetch from ELPA.
git-fetch is the preferred way when there are no stable tarballs.
--
Ricardo
next prev parent reply other threads:[~2019-03-26 10:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 0:24 [bug#34865] [PATCH] Add emacs-zones Brian Leung
2019-03-16 10:56 ` Oleg Pykhalov
2019-03-22 21:37 ` Ludovic Courtès
2019-03-24 20:01 ` Oleg Pykhalov
2019-03-26 9:39 ` Ludovic Courtès
2019-03-26 10:55 ` Ricardo Wurmus [this message]
2019-03-27 10:57 ` Ludovic Courtès
2019-03-27 19:27 ` bug#34865: " Oleg Pykhalov
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=87tvfp52hm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34865@debbugs.gnu.org \
--cc=bkleung89@gmail.com \
--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 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.