From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 3/5] build: Add 'emacs-build-system'
Date: Tue, 07 Jul 2015 19:58:27 +0300 [thread overview]
Message-ID: <87pp43j45o.fsf@gmail.com> (raw)
In-Reply-To: <CAKrPhPO31tDXKceh8ozM2HkXWB-NPxdPJ19aY+hWZ25ivU2u8A@mail.gmail.com> (Federico Beffa's message of "Tue, 7 Jul 2015 09:21:12 +0200")
Federico Beffa (2015-07-07 10:21 +0300) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
>> Wouldn't it be better to name it "elpa-build-system" as that's what it
>> is in my opinion, since it does not retrieve the source directly from
>> upstream but from ELPA/MELPA/... "repositories" instead.
>
> The build system doesn't assume anything about the source location.
>>
>> I imagine there may appear another build system for simple emacs
>> packages (that don't provide Makefile, etc.) that will compile elisp
>> files, generate autoloads and so on. I think it will be a system that
>> should be called "emacs-build-system". WDYT?
>
> That's what the proposed build system does. If it lacks some
> functionality that you think is desirable, I think it is better to add
> it here rather than adding another, almost identical, build system.
Ah, I'm very sorry, You are right; emacs build system and elpa importer
were mixed in my head :-)
A side note: I think generally it would be preferable to use an upstream
release in the package recipe rather than to use a melpa(-stable) URL,
i.e.:
http://foo-upstream.org/foo-0.1.tar.gz instead of
http://stable.melpa.org/packages/foo-0.1.tar
Also along with the concern that melpa stores a tarball only for the
latest package version I think I've found another problem that will
happen with a package from any repository: there are many single-file
packages and these ones are not put in tarballs. I mean the package in
this case is just a simple elisp file, so the 'unpack' will fail.
Look at <http://elpa.gnu.org/packages/rainbow-mode.html> for example:
guix import elpa --archive=gnu rainbow-mode
gives a package that fails on 'unpack' phase.
--
Alex
next prev parent reply other threads:[~2015-07-07 16:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 7:21 [PATCH 3/5] build: Add 'emacs-build-system' Federico Beffa
2015-07-07 16:58 ` Alex Kost [this message]
2015-07-08 20:22 ` Federico Beffa
2015-07-09 8:51 ` Alex Kost
2015-07-09 20:41 ` Federico Beffa
2015-07-10 6:47 ` Alex Kost
2015-07-10 7:43 ` Federico Beffa
2015-07-15 21:52 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2015-06-21 8:31 Federico Beffa
2015-06-21 20:40 ` Alex Kost
2015-06-22 8:51 ` Federico Beffa
2015-06-22 11:49 ` Mathieu Lirzin
2015-06-22 17:59 ` Alex Kost
2015-06-22 19:33 ` Federico Beffa
2015-06-22 19:40 ` Thompson, David
2015-06-23 6:51 ` Federico Beffa
2015-06-25 11:57 ` Ludovic Courtès
2015-06-25 18:39 ` Federico Beffa
2015-06-23 11:57 ` Alex Kost
2015-06-24 16:12 ` Federico Beffa
2015-06-25 12:33 ` Ludovic Courtès
2015-06-25 18:36 ` Federico Beffa
2015-06-27 9:59 ` Ludovic Courtès
2015-07-06 17:47 ` Alex Kost
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=87pp43j45o.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=beffa@ieee.org \
--cc=guix-devel@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.