* The `elpa' branch and single-file package names
@ 2011-05-04 19:58 Stefan Monnier
2011-05-04 20:14 ` Ted Zlatanov
0 siblings, 1 reply; 2+ messages in thread
From: Stefan Monnier @ 2011-05-04 19:58 UTC (permalink / raw)
To: emacs-devel
Currently, in the `elpa' branch, single file package names are of the
form <name>-<version>.el. Having the version there is annoying: E.g. checkdoc
gets confused; we need to "bzr mv" when we change the version numer; ...
I think we should move the version into the file.
The same holds for directory packages, except that checkdoc doesn't get
confused and the version info is already available inside the directory.
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: The `elpa' branch and single-file package names
2011-05-04 19:58 The `elpa' branch and single-file package names Stefan Monnier
@ 2011-05-04 20:14 ` Ted Zlatanov
0 siblings, 0 replies; 2+ messages in thread
From: Ted Zlatanov @ 2011-05-04 20:14 UTC (permalink / raw)
To: emacs-devel
On Wed, 04 May 2011 16:58:46 -0300 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
SM> Currently, in the `elpa' branch, single file package names are of the
SM> form <name>-<version>.el. Having the version there is annoying: E.g. checkdoc
SM> gets confused; we need to "bzr mv" when we change the version numer; ...
SM> I think we should move the version into the file.
Maybe we can make <name>-<version>.el a symlink to <name>.el when the
branch is deployed to the website. I'm OK with any reorganization in
any case.
Ted
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-05-04 20:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-04 19:58 The `elpa' branch and single-file package names Stefan Monnier
2011-05-04 20:14 ` Ted Zlatanov
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).