From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: [PATCH 1/5] gnu: Add emacs-ht.
Date: Sun, 29 Jan 2017 09:07:22 +1100 [thread overview]
Message-ID: <87mvea2605.fsf@zancanaro.id.au> (raw)
In-Reply-To: <878tpw3xgk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On Fri, Jan 27 2017, Ludovic Courtès wrote
> What needs to be done? We cannot guess the upstream URL just from the
> MELPA one, can we?
No, we can't just get it from the URL, but MELPA's recipes should give
us enough information to be able to build them. (After all, they give
MELPA enough information to be able to build them.)
https://github.com/melpa/melpa/tree/master/recipes
I think this is where they're actually processed:
https://github.com/melpa/melpa/blob/8babd80660a50183d81a9269e83c9e473c450ffb/package-build/package-build.el
Carlo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 483 bytes --]
next prev parent reply other threads:[~2017-01-28 22:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 12:31 [PATCH 0/5] Add emacs-mu4e-alert Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 1/5] gnu: Add emacs-ht Mathieu Othacehe
2017-01-27 9:20 ` Alex Kost
2017-01-27 9:59 ` Leo Famulari
2017-01-27 10:16 ` Mathieu OTHACEHE
2017-01-27 19:56 ` Alex Kost
2017-01-27 23:16 ` Ludovic Courtès
2017-01-28 8:18 ` Alex Kost
2017-01-28 9:07 ` Mathieu OTHACEHE
2017-01-30 9:09 ` ELPA importer and upstream URLs Ludovic Courtès
2017-01-30 15:57 ` Mathieu OTHACEHE
2017-01-28 22:07 ` Carlo Zancanaro [this message]
2017-01-26 12:31 ` [PATCH 2/5] gnu: Add emacs-log4e Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 3/5] gnu: Add emacs-gntp Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 4/5] gnu: Add emacs-alert Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 5/5] gnu: Add emacs-mu4e-alert Mathieu Othacehe
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=87mvea2605.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=alezost@gmail.com \
--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 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.