From: Alex Kost <alezost@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: emacs-build-system installs too many files
Date: Fri, 14 Apr 2017 20:16:49 +0300 [thread overview]
Message-ID: <87vaq6zz7i.fsf@gmail.com> (raw)
In-Reply-To: <dd435ec4.AEAAJCRN4gEAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABY8JBz@mailjet.com> (Arun Isaac's message of "Fri, 14 Apr 2017 14:33:35 +0530")
Arun Isaac (2017-04-14 14:33 +0530) wrote:
> The install phase of the emacs-build-system simply copies all files to
> the output directory. This ends up copying many unnecessary files such
> as README, Makefile, tests, hidden files such as .gitignore,
> .travis.yml, etc. MELPA package recipes, on the other hand, copy only a
> subset of the files. This is provided by the :files property in their
> recipe format (https://github.com/melpa/melpa#recipe-format). Quoting
> from their github page:
[...]
> I suggest we modify the emacs-build-system to include a #:files argument
> similar to MELPA's :files property. If others are fine with this, I will
> start working on a patch.
I totally agree! I suggested to remove non-"el[c]" files when Federico
introduced the emacs-build-system. I mentioned it here:
http://lists.gnu.org/archive/html/guix-devel/2015-07/msg00301.html
and a couple of times later :-) But I didn't do anything to implement
this idea, and I think it would be really great if you will give it a
try. Thank you!
--
Alex
next prev parent reply other threads:[~2017-04-14 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 9:03 emacs-build-system installs too many files Arun Isaac
2017-04-14 17:16 ` Alex Kost [this message]
2017-04-19 7:51 ` Arun Isaac
2017-04-19 7:51 ` Arun Isaac
[not found] ` <cu7mvbcq1gy.fsf@systemreboot.net>
2017-05-14 13:45 ` Arun Isaac
2017-05-15 17:19 ` myglc2
2017-05-15 18:46 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vaq6zz7i.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=arunisaac@systemreboot.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).