From: Lynn Winebarger <owinebar@gmail.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Philip Kaludercic <philipk@posteo.net>,
Okamsn <okamsn@protonmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: How to install documentation in sub-directory with Package VC?
Date: Sun, 9 Apr 2023 16:44:48 -0400 [thread overview]
Message-ID: <CAM=F=bCUfu2dn57W87CcrLoPc=ttSZVamSsj9VGnbNtDAMN7=Q@mail.gmail.com> (raw)
In-Reply-To: <87lej0lx1j.fsf@bernoul.li>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On Sun, Apr 9, 2023, 3:11 PM Jonas Bernoulli <jonas@bernoul.li> wrote:
> Philip Kaludercic <philipk@posteo.net> writes:
> Why is :doc needed? I think package-install simply runs makeinfo on all
> texi files, but of course it can rely on them being at the top-level.
> It might end up trying (and failing) to directly process gpl.texi and
> similar. But still, cannot package-vc simply do that too?
>
> The value of :doc can also be an org file and we cannot just blindly try
> to transcode *all* org files to texi.
Is there anything like the info top-level directory node for org files?
My draft of unboxed (package management) has a provision for handling info
files found in an unpacked package, and dealing with texi files when there
is no info file is straightforward. I have no idea what to do with a
random org file used for documenting a package to make it systematically
accessible to the package's user.
Lynn
[-- Attachment #2: Type: text/html, Size: 1561 bytes --]
next prev parent reply other threads:[~2023-04-09 20:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 3:13 How to install documentation in sub-directory with Package VC? Okamsn
2023-03-14 15:56 ` Philip Kaludercic
2023-03-15 9:41 ` Philip Kaludercic
2023-03-16 1:37 ` Okamsn
2023-03-16 8:44 ` Philip Kaludercic
2023-03-28 1:50 ` Okamsn
2023-03-28 7:41 ` Philip Kaludercic
2023-04-02 0:41 ` Okamsn
2023-04-02 5:24 ` Eli Zaretskii
2023-04-05 7:30 ` Philip Kaludercic
2023-04-06 3:52 ` Okamsn
2023-04-06 15:42 ` Philip Kaludercic
2023-04-10 13:39 ` Philip Kaludercic
2023-04-12 0:04 ` Okamsn
2023-04-12 7:27 ` Philip Kaludercic
2023-04-12 7:41 ` Eli Zaretskii
2023-04-12 7:48 ` Philip Kaludercic
2023-04-07 21:46 ` Jonas Bernoulli
2023-04-08 8:36 ` Philip Kaludercic
2023-04-09 18:39 ` Jonas Bernoulli
2023-04-09 20:44 ` Lynn Winebarger [this message]
2023-04-09 21:55 ` Philip Kaludercic
2023-03-28 11:48 ` Eli Zaretskii
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='CAM=F=bCUfu2dn57W87CcrLoPc=ttSZVamSsj9VGnbNtDAMN7=Q@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=okamsn@protonmail.com \
--cc=philipk@posteo.net \
/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).