From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: emacs packaging (emacs-popup)
Date: Wed, 17 Feb 2016 12:52:24 +0300 [thread overview]
Message-ID: <87k2m3ll47.fsf@gmail.com> (raw)
In-Reply-To: <CAKrPhPP0Sgn6AannGiR0bGFz0_ii9gZV5exis6UkYv+K4Xv0Qw@mail.gmail.com> (Federico Beffa's message of "Tue, 16 Feb 2016 08:58:16 +0100")
Federico Beffa (2016-02-16 10:58 +0300) wrote:
> On Mon, Feb 15, 2016 at 5:46 PM, Alex Kost <alezost@gmail.com> wrote:
>> Federico Beffa (2016-02-15 15:12 +0300) wrote:
[...]
>>> I would suggest to move the README.md (and in general documentation
>>> related files) to $datadir/doc/package-name-version/. Info files to
>>> $datadir/info/package-name-version/. Take a look at 'emacs-slime'.
>>>
>>> Remove unused files like .gitignore, ...
>>
>> I don't agree. This is not done for any other emacs package. I think
>> ".gitignore" and other files should not be removed in a package recipe.
>> This is a job for emacs-build-system, and I thought it was agreed¹. So
>> I think this "emacs-popup" package can be left as it is now, and once
>> our emacs-build-system will be improved (to remove useless file, to move
>> README into share/doc, etc.), it will be fixed automatically.
>>
>> ¹ http://lists.gnu.org/archive/html/guix-devel/2015-07/msg00416.html
>
> Doing so will break some packages. One example is 'emacs-slime' which
> includes .lisp and .asd files, other ones are 'emacs-auctex' and
> 'emacs-ob-ipython', ...
For such packages, a potential "cleanup" phase may be removed in a
package recipe. Also I don't think that .lisp, .asd and other files
should be placed in ".../share/emacs/site-lisp/" directory. My
understanding is that this directory (and it's subdirs) should be used
only for elisp files.
> While we could add a phase to remove some pretty common and useless
> files such as .gitignore, in general things are not standardized and
> more complex. Unless upstream fixes this situation it will be
> impossible to make a perfect 'emacs-build-system'.
I think that most packages are simple and very similar, and "cleanup"
phase can just remove everything except *.el[c]. For the complex
packages, this phases can be removed, besides it's likely that the
manual intervention in a package recipe will be required anyway.
Anyway, I'm just talking. Someday (I hope) I will propose patches for
improving emacs-build-system (as I see it).
--
Alex
next prev parent reply other threads:[~2016-02-17 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 12:12 emacs packaging (emacs-popup) Federico Beffa
2016-02-15 16:46 ` Alex Kost
2016-02-15 18:00 ` Nils Gillmann
2016-02-16 7:58 ` Federico Beffa
2016-02-17 9:52 ` Alex Kost [this message]
2016-02-17 20:11 ` Federico Beffa
-- strict thread matches above, loose matches on Subject: below --
2016-02-15 2:26 Nils Gillmann
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=87k2m3ll47.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 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).