From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 37850@debbugs.gnu.org
Subject: bug#37850: Glib documentation is missing
Date: Fri, 25 Oct 2019 23:23:10 +0200 [thread overview]
Message-ID: <87pnikldtt.fsf@gnu.org> (raw)
In-Reply-To: <87wocvwbmy.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 23 Oct 2019 20:38:13 +0200")
Hi,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Marius Bakke <mbakke@fastmail.com> writes:
[...]
>> 'gtk-doc' unsurprisingly depends on GLib, so I'm not sure what the best
>> approach is.
>
> What about the following:
>
> 1. Turn our current glib into glib-minimal.
>
> 2. Build gtk-doc against glib-minimal.
>
> 3. Define a new glib package that inherits from glib-minimal and adds
> gtk-doc as native-inputs so that we can restore the "doc" output.
Alternately, we could define a new “glib-doc” package that would depend
on the current “glib” package, assuming the build system allows us to
build nothing but documentation.
Ludo’.
next prev parent reply other threads:[~2019-10-25 21:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 10:45 bug#37850: Glib documentation is missing Pierre Neidhardt
2019-10-23 18:22 ` Marius Bakke
2019-10-23 18:38 ` Pierre Neidhardt
2019-10-25 21:23 ` Ludovic Courtès [this message]
2019-10-26 9:04 ` Pierre Neidhardt
2019-10-29 10:36 ` Pierre Neidhardt
2019-11-03 16:39 ` Pierre Neidhardt
2019-11-03 19:04 ` Marius Bakke
2019-11-04 9:46 ` Pierre Neidhardt
2019-11-09 23:20 ` Marius Bakke
2019-11-11 9:29 ` Pierre Neidhardt
2019-11-12 12:32 ` pelzflorian (Florian Pelz)
2019-11-12 13:22 ` pelzflorian (Florian Pelz)
2019-11-12 16:00 ` Pierre Neidhardt
2019-11-12 18:34 ` pelzflorian (Florian Pelz)
2019-11-15 11:17 ` Pierre Neidhardt
2019-11-15 12:14 ` pelzflorian (Florian Pelz)
2019-11-15 14:10 ` Marius Bakke
2019-11-15 15:06 ` Pierre Neidhardt
2019-11-21 19:50 ` Marius Bakke
2019-11-27 12:37 ` Pierre Neidhardt
2019-11-09 2:03 ` Alexandros Theodotou
2019-11-09 2:10 ` Alexandros Theodotou
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnikldtt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37850@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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/guix.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).