unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] main 37f7e91: * elpa-packages: Adapt tramp entry.
Date: Tue, 22 Dec 2020 11:04:36 -0500	[thread overview]
Message-ID: <jwv4kkd4z0x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20201222135723.3573020B72@vcs0.savannah.gnu.org> (Michael Albinus's message of "Tue, 22 Dec 2020 08:57:22 -0500 (EST)")

> + ("tramp"		:url "git://git.sv.gnu.org/tramp.git"
> +  :branch "externals/tramp"
> +  :main-file "trampver.el"
> +  :make ("autoloads" "info")
> +  :doc "tramp.info")

Hmm... admin/README says:

    ** =:make TARGET=
    Indicates that we should run ~make TARGET~ in order to build some files.
    This is run before processing =:doc=, so it can be used to generate
    the Info and Texinfo file from some other format.
    TARGET can also be a list, in which case each target should be
    an actual file name (rather than a "phony target").

so it should be either something like:

    :make ("tramp-loaddefs.el" "tramp.info")

or something like:

    :make "elpa"

BTW, regarding `:doc`, IIUC the difference between `:doc "text/tramp.texi"`
and your makefile rules seems to be mostly `--footnote-style=end`.  I'm not
familiar enough with Info and `makeinfo` to know what this does.
Do you think we should maybe use `--footnote-style=end` by default?


        Stefan




       reply	other threads:[~2020-12-22 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201222135721.29566.13130@vcs0.savannah.gnu.org>
     [not found] ` <20201222135723.3573020B72@vcs0.savannah.gnu.org>
2020-12-22 16:04   ` Stefan Monnier [this message]
2020-12-22 17:48     ` [elpa] main 37f7e91: * elpa-packages: Adapt tramp entry Michael Albinus
2020-12-22 18:09       ` Stefan Monnier
2020-12-22 18:23         ` Michael Albinus

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv4kkd4z0x.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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/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).