all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Vasile Dumitrascu <va511e@yahoo.com>
Cc: Alex Kost <alezost@gmail.com>, 26268@debbugs.gnu.org
Subject: bug#26268: [PATCH] gnu: Add emacs-idle-highlight.
Date: Thu, 30 Mar 2017 10:49:45 +0200	[thread overview]
Message-ID: <87y3vn409i.fsf@gnu.org> (raw)
In-Reply-To: <68dcc0d8-ee90-ae6d-b47d-f17c4bfa3e3f@yahoo.com> (Vasile Dumitrascu's message of "Tue, 28 Mar 2017 18:59:00 +0000")

Hi Vasile,

Vasile Dumitrascu <va511e@yahoo.com> skribis:

>   I agree with your observations. To explain my previous choice: I was
> using melpa as source for the packages as I have found the option to
> import from melpa in
> https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-import
> so I thought that this is the recommended approach. The document should
> be updated to mention this as not recommended for contributions, for the
> reasons you have mentioned.
>
>   Maybe rather we should have a predefined import task that easily
> imports from github or git based repositories (I could not find one in
> the docs).

You’re right, there’s no such thing.

The difficulty here is that the importer gets package info from
melpa.org (or elpa.gnu.org) and AIUI, this info does not include the URL
of the upstream repo.  That’s why we have to do that step manually,
which is arguably suboptimal.

Not sure how to improve it.

Thoughts?

Ludo’.

  reply	other threads:[~2017-03-30  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170326233912.23146-1-va511e@yahoo.com>
2017-03-27  8:54 ` bug#26268: [PATCH] gnu: Add emacs-idle-highlight Alex Kost
2017-03-28 18:59   ` Vasile Dumitrascu
2017-03-30  8:49     ` Ludovic Courtès [this message]
2017-03-28 20:12 ` Vasile Dumitrascu
2017-03-29 11:40   ` Catonano
2017-03-29 11:59     ` Vasile Dumitrascu
2017-03-30  8:53   ` Ludovic Courtès

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=87y3vn409i.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26268@debbugs.gnu.org \
    --cc=alezost@gmail.com \
    --cc=va511e@yahoo.com \
    /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.