From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 26786@debbugs.gnu.org
Subject: bug#26786: [PATCH] gnu: emacs-org: Update to 20170502.
Date: Sat, 06 May 2017 15:47:01 +0200 [thread overview]
Message-ID: <874lwyw10q.fsf@gnu.org> (raw)
In-Reply-To: <8082ba63.AEQAKHOcDVMAAAAAAAAAAAO7_ZEAAAACwQwAAAAAAAW9WABZDUwM@mailjet.com> (Arun Isaac's message of "Sat, 06 May 2017 09:37:08 +0530")
Arun Isaac <arunisaac@systemreboot.net> skribis:
>>> I think we should build directly from org's release tarball at
>>> http://orgmode.org/org-9.0.6.tar.gz instead of using the ELPA
>>> tarball. It somehow feels like we are not building from source but
>>> rather relying on a prepackaged tarball from ELPA. However, Nicolas
>>> Goaziou, the org mode maintainer,
>>> disagrees. https://lists.gnu.org/archive/html/guix-devel/2016-08/msg01395.html
>>
>> I find Nicolas’s argument above (that building from ELPA makes the
>> recipe trivial) pretty convincing.
>>
>> Why would you suggest using the tarball from orgmode.org?
>
> It seems like we are depending on an intermediary (ELPA) instead of
> directly building from the original source. I feel that Guix packages
> should not depend on other repositories (like ELPA).
I agree with this sentiment, but my understanding is that ELPA is not
really an “intermediary”: package maintainers upload directly there, and
some upload only there. So I think it’s OK. Thoughts?
Ludo’.
next prev parent reply other threads:[~2017-05-06 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 17:43 bug#26786: [PATCH] gnu: emacs-org: Update to 20170502 Vasile Dumitrascu
2017-05-05 20:45 ` Arun Isaac
2017-05-05 22:06 ` Ludovic Courtès
2017-05-06 4:07 ` Arun Isaac
2017-05-06 13:47 ` Ludovic Courtès [this message]
2017-05-06 16:59 ` Arun Isaac
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=874lwyw10q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26786@debbugs.gnu.org \
--cc=arunisaac@systemreboot.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.