From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: `make' written in elisp
Date: 04 Jan 2004 18:25:03 -0500 [thread overview]
Message-ID: <jwvbrpjnvve.fsf-monnier+emacs/devel@asado.iro.umontreal.ca> (raw)
In-Reply-To: <pa67fsr6amg8$.4p3gjtb4y4i9.dlg@40tude.net>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
> For most users of Emacs who are not on *ix, it is harder to install new
> packages than for those on *ix since most (GNU) Emacs "extensions" are
> shipped with makefiles or autoconf scripts. This works flawlessly on Unix
> but not on other systems - especially because most of the simpler scripts
> make assumptions where your emacs binary or your site-lisp directory is.
> You can adjust this for every single package, but what for? most makefiles
> don't do more than runninge batch-byte-compile for the .el files, makeinfo
> for the .texi files and install-info for the resulting info files (plus
> copying the files where they belong).
For the same reason, I wrote the install.el elisp package which can take
a single .el file or a tarball of an elisp package and install it.
It is a completely different solution to your problem, but I think that
your code addresses just the issues that are left in install.el.
It's still very simple (or rather: simplistic) and needs more work, but it
might be interesting to integrate it with your code.
I have attached my latest install.el.
Stefan
[-- Attachment #2: install.el --]
[-- Type: application/emacs-lisp, Size: 21208 bytes --]
[-- Attachment #3: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2004-01-04 23:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 19:31 `make' written in elisp Michael Schierl
2003-12-31 22:57 ` Richard Stallman
2003-12-31 23:14 ` Michael Schierl
2004-01-01 21:10 ` Richard Stallman
2004-01-01 21:37 ` Michael Schierl
2004-01-04 23:25 ` Stefan Monnier [this message]
2005-01-02 16:06 ` Richard Stallman
2005-01-02 23:22 ` David Kastrup
2005-01-02 23:55 ` Ralf Angeli
2005-01-03 0:07 ` David Kastrup
2005-01-03 0:25 ` Ralf Angeli
2005-01-03 4:32 ` Richard Stallman
2005-01-03 8:02 ` David Kastrup
2005-01-03 9:36 ` Eli Zaretskii
2005-01-03 16:45 ` Stefan Monnier
2005-01-03 9:10 ` Ralf Angeli
2005-01-03 18:29 ` Richard Stallman
2005-01-03 19:28 ` Ralf Angeli
2005-01-03 23:10 ` David Kastrup
2005-01-04 3:38 ` Richard Stallman
2005-01-04 11:17 ` Ralf Angeli
2005-01-03 0:26 ` Stefan
2005-01-03 11:05 ` Stephen J. Turnbull
2005-01-03 17:16 ` Stefan Monnier
2005-01-04 12:00 ` Stephen J. Turnbull
2005-01-04 13:59 ` Stefan
2005-01-04 14:07 ` Miles Bader
2004-03-31 22:31 ` patch for locate-file-completion? Nic Ferrier
2004-04-01 17:34 ` Richard Stallman
[not found] <E1CloEh-0004Sl-Hg@monty-python.gnu.org>
2005-01-04 16:10 ` `make' written in elisp Eric M. Ludlam
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=jwvbrpjnvve.fsf-monnier+emacs/devel@asado.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.