all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: document package.el
Date: Sat, 21 Aug 2010 12:22:56 -0600	[thread overview]
Message-ID: <m362z3vn9b.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83bp9ex3ro.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Aug 2010 10:47:55 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Tom> I finally found a little time to write some documentation for
Tom> package.el.
[...]

Eli> At this point I wondered why nothing is done with the Author and
Eli> Maintainer headers.

They weren't needed by the package manager.

Tom> +  A multi-file package is just a @file{.tar} file.

Eli> Does package.el really support only .tar files?  That sounds like an
Eli> unnecessary limitation, since Emacs supports much more.

Emacs doesn't have built-in support for anything else.  It relies on
external programs.  Since I think it is best not to rely on the
environment this way, I purposely limited package.el.  I still think
this was a good decision, because it only affects packagers, not users.
I don't know of any gain to be had by expanding this.

In any case I wrote the documentation to describe what exists now.

Eli> If this means a multi-file package cannot have a long description in
Eli> the form of "Commentary", then this sounds like an inconvenience,
Eli> e.g., if a package starts as a single file and then develops into a
Eli> multi-file one.

The problem is knowing which file to extract this information from.
It is not uncommon for several files to have comment headers.

Tom> +  If the package has an info manual, you should distribute the needed
Tom> +info files, plus a @file{dir} file made with @command{install-info}.

Eli> Not clear why the `dir' file is needed.  Are you trying to support
Eli> users that don't have install-info on their systems?

Yes.

Tom



  parent reply	other threads:[~2010-08-21 18:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 22:42 document package.el Tom Tromey
2010-08-06 23:48 ` Phil Hagelberg
2010-08-09 16:22   ` Tom Tromey
2010-08-07  1:43 ` Christoph
2010-08-07  8:57   ` Geralt
2010-08-09 16:23   ` Tom Tromey
2010-08-26 23:27   ` Juri Linkov
2010-08-26 23:50     ` Stefan Monnier
2010-08-27  3:14       ` Christoph
2010-08-27  5:51         ` Uday S Reddy
2010-08-27  3:12     ` Christoph
2010-08-27  7:07     ` Uday S Reddy
2010-08-27 21:40       ` Phil Hagelberg
2010-08-28 17:34         ` Tom Tromey
2010-08-27  6:43   ` Uday S Reddy
2010-08-27 15:51     ` Tom Tromey
2010-08-27 16:17     ` Chong Yidong
2010-08-27 21:43     ` Richard Stallman
2010-08-27 22:58       ` Christoph
2010-08-28  7:25         ` Uday S Reddy
2010-08-07  7:47 ` Eli Zaretskii
2010-08-08 22:39   ` Chong Yidong
2010-08-09 16:24     ` Tom Tromey
2010-08-21 18:22   ` Tom Tromey [this message]
2010-08-21 18:51     ` Eli Zaretskii
2010-08-22  1:40       ` Tom Tromey
2010-08-08 23:06 ` Chong Yidong
2010-08-09 21:13   ` Tom Tromey
2010-08-21 18:37   ` Tom Tromey
2010-08-25 17:24     ` Chong Yidong
2010-08-25 17:34       ` Tom Tromey
2010-08-25 17:35         ` Chong Yidong
2010-08-17 14:37 ` Uday S Reddy
2010-08-17 15:57   ` Tom Tromey

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=m362z3vn9b.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --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.