all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu OTHACEHE <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>,
	Carlo Zancanaro <carlo@zancanaro.id.au>
Subject: Re: ELPA importer and upstream URLs
Date: Mon, 30 Jan 2017 16:57:35 +0100	[thread overview]
Message-ID: <87k29ck0b4.fsf@gmail.com> (raw)
In-Reply-To: <871svkhq2z.fsf_-_@gnu.org>


> The difficulty is that we need both the Git URL and a commit ID.  Is the
> commit ID available?

I can't find it at first glance, maybe with github API ?

>
> If we have all of that ‘guix import elpa’ could just extract that data
> and generate the right thing.  For packages that don’t have a URL/commit
> associated with them, it could just keep doing the same as now.
>
> WDYT?  Would you or Carlo like to give it a try?  :-)

I'm ok to do it but I'll be afk next couple of weeks.

Mathieu

  reply	other threads:[~2017-01-30 15:57 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 [this message]
2017-01-28 22:07             ` [PATCH 1/5] gnu: Add emacs-ht Carlo Zancanaro
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=87k29ck0b4.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=alezost@gmail.com \
    --cc=carlo@zancanaro.id.au \
    --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.