From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Andrew Tropin <andrew@trop.in>
Cc: 57280@debbugs.gnu.org
Subject: [bug#57280] [PATCH 0/3] Add documentation-files argument to emacs build system.
Date: Mon, 29 Aug 2022 18:38:22 +0200 [thread overview]
Message-ID: <6f1b7bc2361cd375ee54abbeb1e9c4091329283b.camel@gmail.com> (raw)
In-Reply-To: <87mtbr13dd.fsf@trop.in>
Am Freitag, dem 26.08.2022 um 17:33 +0300 schrieb Andrew Tropin:
> > > >
> > Cheers
>
> I went through a few popular packages and came up with conclusion
> that it's hard to make good heuristic for automatical documentation
> build:
>
> 1. I tried (find-files "." "\\.(texi|txi|texinfo)$") with consequent
> for-each and it doesn't work in general case because it will build
> files intended for inclusion, not standalone building.
Fair enough, there's probably similar issues with org etc. That said,
wouldn't the top-level info/org/whatever file share the package name?
> 2. Adding automatic documentation build phase also means that almost
> all emacs packages will be rebuild
That's why I'm currently delaying native-comp until all other changes
to emacs-build-system are done.
> It seems that manual approach is more precise, less intrusive and
> helps to get rid of many custom and non-uniform documentation build
> phases.
If you're going for a "manual" approach, I'd suggest instead making a
curried ((build-documentation #:texinfo-files #:texinfo-regexp ...)
#:outputs ...) so that the files can be written directly into the (add-
after ...) syntax.
Cheers
next prev parent reply other threads:[~2022-08-29 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wnb5lhyr.fsf@trop.in>
[not found] ` <107d9c475d47842d67db4f0a7d85d63ae11f9f3c.camel@gmail.com>
2022-08-19 3:33 ` [bug#57280] [PATCH 0/3] Add documentation-files argument to emacs build system Andrew Tropin
2022-08-19 4:19 ` Liliana Marie Prikler
2022-08-19 6:21 ` Andrew Tropin
2022-08-19 15:39 ` Liliana Marie Prikler
2022-08-26 14:33 ` Andrew Tropin
2022-08-29 16:38 ` Liliana Marie Prikler [this message]
2022-08-30 8:15 ` Andrew Tropin
2022-08-30 8:28 ` Liliana Marie Prikler
2022-08-31 9:36 ` Andrew Tropin
2022-08-31 10:07 ` Liliana Marie Prikler
2022-09-02 14:02 ` Andrew Tropin
2022-09-02 14:52 ` Liliana Marie Prikler
2023-04-26 4:40 ` bug#57280: " Andrew Tropin
2022-08-18 18:35 [bug#57280] " Andrew Tropin
2022-08-18 19:31 ` Liliana Marie Prikler
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=6f1b7bc2361cd375ee54abbeb1e9c4091329283b.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=57280@debbugs.gnu.org \
--cc=andrew@trop.in \
/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/guix.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.