FS#17719 - [hal] Package fails to build outside chroot
Attached to Project:
Arch Linux
Opened by Michael Witten (mfwitten) - Wednesday, 06 January 2010, 04:52 GMT
Last edited by Jan de Groot (JGC) - Sunday, 07 March 2010, 13:43 GMT
Opened by Michael Witten (mfwitten) - Wednesday, 06 January 2010, 04:52 GMT
Last edited by Jan de Groot (JGC) - Sunday, 07 March 2010, 13:43 GMT
|
Details
The tool `gtkdoc-fixxref' of package `gtk-doc' now requires
a `--module=' flag. The hal 0.5.15-1 source doesn't provide
this flag when trying to build the gtk-doc hal
documentation.
There are 2 ways to solve this problem. Given that the gtk-doc hal documentation is a bunch of poorly written API nonsense at which nobody ever looks, the easiest solution would be to build hal without the gtk-doc step, which requires just adding the `--disable-gtk-doc' flag to the `./configure' line in the PKGBUILD's build() function. For this first solution, just apply the provided `solutions/0/PKGBUILD.patch' to the hal package's PKGBUILD. However, if it is for some reason desirable to provide this gtk-doc hal documentation, then first apply the provided `solutions/1/PKGBUILD.patch' (NOTE, that's solutions/**1**), and secondly place `solutions/1/FIXXREF_OPTIONS-module.patch' among the other patches that are shipped with the hal package's PKGBUILD. |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 07 March 2010, 13:43 GMT
Reason for closing: Fixed
Additional comments about closing: Package builds with --disable-gtk-doc now. This still includes gtk-doc documentation but doesn't rebuild the documentation.
Sunday, 07 March 2010, 13:43 GMT
Reason for closing: Fixed
Additional comments about closing: Package builds with --disable-gtk-doc now. This still includes gtk-doc documentation but doesn't rebuild the documentation.
(1) somebody isn't building it in a chroot where gtk-doc isn't installed,
(2) gtkdoc-fixxref wasn't a problem at some point; it now is a problem, requiring a fix, especially since no new hal release is planned (so I've heard on #hal).
(3) In my opinion, PKGBUILD's shouldn't require users to setup wonky environments like clean-room chroots.
I painstakingly went to the trouble of including a solution that still allows gtk-doc hal documentation to be built if gtk-doc is installed, all of which is already described above.
I'll close as "won't implement" on April 2010 bug day unless some new information or discourse appears.
There's nothing to implement; I've already done all the work.
Just take what I've done and use it.