From: Arun Isaac <arunisaac@systemreboot.net>
To: Alex Kost <alezost@gmail.com>
Cc: 26802@debbugs.gnu.org
Subject: bug#26802: Single source file emacs packages get a ".el.el" extension
Date: Mon, 15 May 2017 18:58:29 +0530 [thread overview]
Message-ID: <eac56466.AEQAKZSU7kQAAAAAAAAAAAO9aM4AAAACwQwAAAAAAAW9WABZGa0d@mailjet.com> (raw)
In-Reply-To: <8737c7fjgn.fsf@gmail.com>
> I'm not sure, I think:
>
> - it's too much for all the sources, as the upstream source may not
> contain a version in the file name at all. Do we really want to raise a
> warning in this case?
> - and it's not enough for ".el" sources, I mean "something-version.el"
> is not enough, as the file name must exactly be "name-version.el" (as it
> is with ELPA single-filed sources), so the emacs-build-system will
> output "name.el" file which will correspond to 'name' feature provided
> by this file.
You have a point, but...
If all packages cannot be expected to have "name-version", then it is
unreasonable and arbitrary to only expect single source file emacs
packages to have a filename of this format. Instead, the emacs build
system should be made more robust so that it can tolerate a souce file
name like "web-mode.el" and still produce the correct installation path.
next prev parent reply other threads:[~2017-05-15 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 12:51 bug#26802: Single source file emacs packages get a ".el.el" extension Arun Isaac
2017-05-09 19:38 ` Alex Kost
2017-05-11 19:19 ` Arun Isaac
2017-05-13 8:54 ` Alex Kost
2017-05-13 16:36 ` Arun Isaac
2017-05-14 17:15 ` Alex Kost
2017-05-15 13:28 ` Arun Isaac [this message]
2017-05-16 17:29 ` Alex Kost
2017-05-17 17:04 ` Arun Isaac
2017-05-21 9:03 ` Alex Kost
2017-05-13 5:23 ` bug#26802: [PATCH 1/3] gnu: emacs-goto-chg: Set source file-name Arun Isaac
2017-05-13 8:55 ` Alex Kost
2017-05-17 16:52 ` bug#26802: [PATCH 1/4] gnu: lint: Fix typo Arun Isaac
2017-05-18 11:28 ` 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=eac56466.AEQAKZSU7kQAAAAAAAAAAAO9aM4AAAACwQwAAAAAAAW9WABZGa0d@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=26802@debbugs.gnu.org \
--cc=alezost@gmail.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.