After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 688271 - build: Add --disable-man option
build: Add --disable-man option
Status: RESOLVED FIXED
Product: gnome-session
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-11-13 18:13 UTC by Colin Walters
Modified: 2012-11-20 01:50 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build: Add --disable-man option (2.15 KB, patch)
2012-11-13 18:13 UTC, Colin Walters 		none Details | Review
build: Add --disable-man option (2.14 KB, patch)
2012-11-13 19:15 UTC, Colin Walters 		none Details | Review

Description Colin Walters 2012-11-13 18:13:43 UTC 
1) For embedded systems, it makes no sense to include documentation
   of this kind on each image.  So we might as well not even build
   it.
2) For people bootstrapping systems from source code, documentation
   is the source of many cyclical build loops.  Allowing it to
    be disabled helps cut these loops.
3) The Docbook stylesheets and build system have no sane upstream,
   and so at the moment aren't included in gnome-ostree.
Comment 1 Colin Walters 2012-11-13 18:13:46 UTC 
Created attachment 228910 [details] [review]
build: Add --disable-man option
Comment 2 William Jon McCann 2012-11-13 18:16:08 UTC 
Do we need the man pages? Maybe this should be --enable-man instead?
Comment 3 Colin Walters 2012-11-13 19:04:13 UTC 
(In reply to comment #2)
> Do we need the man pages? Maybe this should be --enable-man instead?

Well...we have variants of this patch in a lot of modules now, like dconf, gdm, gnome-shell, etc... at this point I think I'd rather be consistent.
Comment 4 William Jon McCann 2012-11-13 19:06:56 UTC 
Even more reason to do it the other way around I think. To make it easier and slimmer by default.
Comment 5 Colin Walters 2012-11-13 19:15:22 UTC 
Created attachment 228920 [details] [review]
build: Add --disable-man option

Now defaulting to no
Comment 6 Matthias Clasen 2012-11-20 01:50:14 UTC 
I pushed the first patch - man pages are useful; I don't see any reason not to build them by default.