From: Marius Bakke <mbakke@fastmail.com>
To: "Pierre Neidhardt" <mail@ambrevar.xyz>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 37850@debbugs.gnu.org
Subject: bug#37850: Glib documentation is missing
Date: Sun, 03 Nov 2019 20:04:28 +0100 [thread overview]
Message-ID: <8736f4ok77.fsf@devup.no> (raw)
In-Reply-To: <87k18gncbn.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> From 893613a3b99c20688cc331d2926dbee28cc143d7 Mon Sep 17 00:00:00 2001
> From: Pierre Neidhardt <mail@ambrevar.xyz>
> Date: Sun, 3 Nov 2019 17:36:17 +0100
> Subject: [PATCH] gnu: Add glib-minimal and build glib doc.
>
> glib documentation must be built with gtk-doc which in turn depends on glib,
> so we need to define glib-minimal which does not depend on gtk-doc.
>
> * gnu/packages/glib.scm (glib-minimal): New variable.
> (glib)[source]: Don't use `name'.
> * gnu/packages/avahi.scm: Use glib-minimal when necessary.
> * gnu/packages/cups.scm: Use glib-minimal when necessary.
> * gnu/packages/gnome.scm: Use glib-minimal when necessary.
> * gnu/packages/graphviz.scm: Use glib-minimal when necessary.
> * gnu/packages/gtk.scm: Use glib-minimal when necessary.
> * gnu/packages/inkscape.scm: Use glib-minimal when necessary.
> * gnu/packages/pdf.scm: Use glib-minimal when necessary.
Please mention all changed variables and inputs here, as we always do.
That said, I'm not certain this is a good solution. Why do some
packages use glib-minimal and others not? What does "necessary" mean in
this context?
What about 'hiding' the normal glib package, and expose a
'glib-with-documentation' variant to end users, similar to how the
'cmake' package works?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-03 19:05 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
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 [this message]
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=8736f4ok77.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=37850@debbugs.gnu.org \
--cc=ludo@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).