From: Federico Beffa <beffa@ieee.org>
To: Alex Kost <alezost@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: emacs packaging (emacs-popup)
Date: Tue, 16 Feb 2016 08:58:16 +0100 [thread overview]
Message-ID: <CAKrPhPP0Sgn6AannGiR0bGFz0_ii9gZV5exis6UkYv+K4Xv0Qw@mail.gmail.com> (raw)
In-Reply-To: <87a8n1rkex.fsf@gmail.com>
On Mon, Feb 15, 2016 at 5:46 PM, Alex Kost <alezost@gmail.com> wrote:
> Federico Beffa (2016-02-15 15:12 +0300) wrote:
>
>> Nils Gillmann <niasterisk@grrlz.net> writes:
>>
>>> I'm packaging emacs-popup.
>>>
>>> Currently the output builds with
>>> niasterisk@khazad-dum ~/projects/guix_project/guix$ ls -al
>>> /gnu/store/knpjk9vflja0i6yhnz4ai57k29jpgm4p-emacs-popup-0.5.3/share/emacs/site-lisp/guix.d/popup-0.5.3/
>>> total 180
>>> dr-xr-xr-x 4 root guixbuild 4096 Jan 1 1970 ./
>>> dr-xr-xr-x 3 root guixbuild 4096 Jan 1 1970 ../
>>> -r--r--r-- 2 root guixbuild 90 Jan 1 1970 Cask
>>> dr-xr-xr-x 3 root guixbuild 4096 Jan 1 1970 etc/
>>> -r--r--r-- 2 root guixbuild 14 Jan 1 1970 .gitignore
>>> -r--r--r-- 2 root guixbuild 626 Jan 1 1970 Makefile
>>> -r--r--r-- 2 root guixbuild 334 Jan 1 1970 popup-autoloads.el
>>> -r--r--r-- 2 root guixbuild 54848 Jan 1 1970 popup.el
>>> -r--r--r-- 2 root guixbuild 75474 Jan 1 1970 popup.elc
>>> -r--r--r-- 2 root guixbuild 10187 Jan 1 1970 README.md
>>> dr-xr-xr-x 2 root guixbuild 4096 Jan 1 1970 tests/
>>> -r--r--r-- 2 root guixbuild 569 Jan 1 1970 .travis.yml
>>>
>>> Can this be improved, ie remove some of the files to clean it up,
>>> or is it all good?
>>
>> 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', ...
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'.
Checking the code to remind myself of the details, the only thing
about non .el files that it does, is to move info files to the
appropriate directory.
Regards,
Fede
next prev parent reply other threads:[~2016-02-16 7:58 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 [this message]
2016-02-17 9:52 ` Alex Kost
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=CAKrPhPP0Sgn6AannGiR0bGFz0_ii9gZV5exis6UkYv+K4Xv0Qw@mail.gmail.com \
--to=beffa@ieee.org \
--cc=alezost@gmail.com \
--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).