1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] RFC: gtk-doc proposed changes
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20gtk-doc%20proposed%20changes&In-Reply-To=%3CCAJmd%2BxpaJCKuJfzoGr%2Bd5xOQ8gp9fKWAmbtQA25ULQMTW8s31A%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006962.html">
<LINK REL="Next" HREF="006964.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] RFC: gtk-doc proposed changes</H1>
<B>Ahmad Samir</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20gtk-doc%20proposed%20changes&In-Reply-To=%3CCAJmd%2BxpaJCKuJfzoGr%2Bd5xOQ8gp9fKWAmbtQA25ULQMTW8s31A%40mail.gmail.com%3E"
TITLE="[Mageia-dev] RFC: gtk-doc proposed changes">ahmadsamir3891 at gmail.com
</A><BR>
<I>Fri Jul 22 13:39:00 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006962.html">[Mageia-dev] RFC: gtk-doc proposed changes
</A></li>
<LI>Next message: <A HREF="006964.html">[Mageia-dev] [RPM] cauldron core/release mgarepo-1.9.11-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6963">[ date ]</a>
<a href="thread.html#6963">[ thread ]</a>
<a href="subject.html#6963">[ subject ]</a>
<a href="author.html#6963">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 22 July 2011 13:24, Christiaan Welvaart <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">cjw at daneel.dyndns.org</A>> wrote:
><i> On Fri, 22 Jul 2011, Ahmad Samir wrote:
</I>><i>
</I>>><i> ATM gtk-doc requires dblatex which requires texlive -> texlive-texmf;
</I>>><i> due to the outrageous size of texlive-texmf, building packages in
</I>>><i> local chroots becomes a bit of pain/burden on my HDD, also each of
</I>>><i> texlive and xmltex have I/O intensive postinstall scriptlets.
</I>><i>
</I>><i> The best solution for that may be to put the chroot in a tmpfs.
</I>><i>
</I>>><i> I see the texlive-texmf issue is being discussed in another thread so
</I>>><i> I'll keep this one about gtk-doc; here're a couple of points:
</I>><i>
</I>><i> Too bad since this appears to be strongly related to the gtk-doc issue you
</I>><i> mention. I mean, providing a minimal set of texlive packages may fix this
</I>><i> gtk-doc problem.
</I>><i>
</I>>><i> - Some packages have BR gtk-doc but it's redundant:
</I>>><i>  o They don't have --enable-gtk-doc passed to ./configure, which
</I>>><i> means that BR isn't used at all
</I>>><i>  o Most of those packages already bundle html gtk-doc's; is there any
</I>>><i> benefit rebuilding those docs when building the package? or should the
</I>>><i> gtk-doc BR get dropped in such cases (since no one complained about
</I>>><i> those html docs all those years)?
</I>><i>
</I>><i> In general I think it's best to generate everything from original sources
</I>><i> [1]. It makes sure all build scripts/code/documentation is generated using
</I>><i> the tools in the distro which may be newer and/or have patches compared to
</I>><i> the tools used to generate the files shipped with the source code. It also
</I>><i> ensures we can support such packages, because when someone reports a bug in
</I>><i> a generated file we should never patch that file directly but its source.
</I>><i>
</I>>><i> - I am thinking of splitting gtk-doc itself, putting gtkdoc-mkpdf in a
</I>>><i> separate sub-package which will require dblatex:
</I>>><i>  o AFAICS dblatex is only used for creating PDF's from XML sources,
</I>>><i> so only useful for gtkdoc-mkpdf
</I>><i>
</I>><i> Interesting.
</I>><i>
</I>>><i>  o This will result in less HDD grinding due to texlive-texmf and
</I>>><i> xmltex being, unnecessarily, pulled in chroots (either local ones or
</I>>><i> on the BS). Note that for most of the packages I saw,
</I>>><i> --enable-gtk-doc-html is the default (assuming only --enable-gtk-doc
</I>>><i> was passed to configure).
</I>>><i>  o I don't see any packages with pdf gtk-doc documentation:
</I>>><i>  $ urpmf /usr/share/gtk-doc | grep pdf
</I>>><i>
</I>>><i>  gives nothing at all.
</I>>><i>
</I>>><i> So, theoretically, this split shouldn't break any packages (there're
</I>>><i> 144 SRPMS that have BR gtk-doc and 5 -devel packages that require
</I>>><i> gtk-doc). And if any package breaks due to the split, the fix is
</I>>><i> simply adding BR gtk-doc-pdf. Of course we can make it more painful
</I>>><i> and require that those 149 packages get a test build before the split
</I>>><i> is OK'ed...
</I>><i>
</I>><i> Maybe we should first set as policy to provide HTML developer documentation
</I>><i> and not PDFs when there is a choice.
</I>
That policy has been implicitly in effect for a very long time, I
couldn't find a single gtk-doc pdf....
><i> Note however that HTML docs generated
</I>><i> by doxygen can take a lot of space.
</I>><i>
</I>
Yes; but that's a different issue, texlive* takes a lot of time to
install but builds pdf's fast; doxygen is vice versa, installs quickly
but takes a long time to build the docs sometimes...
><i>
</I>><i>
</I>><i>    Christiaan
</I>><i>
</I>><i>
</I>><i> [1] that's why I'd like to ask you not to remove any
</I>><i> autoreconf/autotools/etc. calls from %build (:
</I>><i>
</I>><i>
</I>
You're talking about gnome-control-center? I thought autoreconf was
run by mistake, as the old comment said it must be run for patch19
which hasn't applied for some time.
But indeed, there should be a clear policy about that: either we
execute autoreconf/autotool.. etc for all packages (make
%configure2_5x run it or something), or we only run it when needed for
e.g. a patch or a package that has an old/new libtool than our
libtool....
--
Ahmad Samir
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006962.html">[Mageia-dev] RFC: gtk-doc proposed changes
</A></li>
<LI>Next message: <A HREF="006964.html">[Mageia-dev] [RPM] cauldron core/release mgarepo-1.9.11-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6963">[ date ]</a>
<a href="thread.html#6963">[ thread ]</a>
<a href="subject.html#6963">[ subject ]</a>
<a href="author.html#6963">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
