From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Tassilo Horn <tsdh@gnu.org>, emacs-devel@gnu.org
Subject: Re: [elpa] externals/auctex f124fe7d28: Release GNU AUCTeX 14.0.3
Date: Wed, 21 Feb 2024 17:07:20 +0000 [thread overview]
Message-ID: <87il2hwxtj.fsf@posteo.net> (raw)
In-Reply-To: <jwv34tl6b3v.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 21 Feb 2024 11:24:06 -0500")
Philip Kaludercic <philipk@posteo.net> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>> Because back then, `elpa.gnu.org` was not able to generate them.
>>>> Nowadays, we could use
>>>>
>>>> :doc "doc/auctex.texi"
>>>>
>>>> in the spec instead.
>>>
>>> Can :doc be a list? Because there's also preview-latex.texi.
>>
>> Yes.
>>
>>> Does that mean the ELPA devel package could be built from our master
>>> branch always reflecting that and the normal package, too, after version
>>> bumps?
>>
>> Almost.
>>
>>> Well, at least in theory after adding a Version header and somehow
>>> setting the version when generating auctex.el from auctex.el.in?
>>
>> That's right: we still need the `auctex.el` file to be in Git and to
>> contain the `Version:` thingy.
>
> Another idea might be to have a separate :main-file for versioning, if
> there is an advantage in building auctex.el while preparing the package.
Never mind this, I missed Stefan's message.
>>
>> Stefan
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Well, at least in theory after adding a Version header and somehow
>>> setting the version when generating auctex.el from auctex.el.in?
>>
>> That's right: we still need the `auctex.el` file to be in Git and to
>> contain the `Version:` thingy.
>
> Tho, it could actually be another file (e.g. for Tramp we have
> `:main-file "trampver.el"`).
>
> Stefan
next prev parent reply other threads:[~2024-02-21 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170844508291.3153.9183498620897065719@vcs2.savannah.gnu.org>
[not found] ` <20240220160445.7C360C00227@vcs2.savannah.gnu.org>
2024-02-20 16:43 ` [elpa] externals/auctex f124fe7d28: Release GNU AUCTeX 14.0.3 Philip Kaludercic
2024-02-21 12:06 ` Tassilo Horn
2024-02-21 13:00 ` Stefan Monnier
2024-02-21 14:26 ` Tassilo Horn
2024-02-21 15:01 ` Stefan Monnier
2024-02-21 16:24 ` Stefan Monnier
2024-02-21 17:07 ` Philip Kaludercic [this message]
2024-02-21 17:50 ` Stefan Monnier
2024-02-21 17:02 ` Philip Kaludercic
2024-02-21 20:21 ` Tassilo Horn
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=87il2hwxtj.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tsdh@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 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).