Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

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.
Comment by Jan de Groot (JGC) - Wednesday, 06 January 2010, 07:53 GMT
Technically there's nothing wrong with hal or the PKGBUILD, as it builds fine in a chroot where gtk-doc isn't installed.
Comment by Michael Witten (mfwitten) - Wednesday, 06 January 2010, 08:13 GMT
However, the official hal package *does* install gtk-doc hal documentation, so:

(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.
Comment by Jan de Groot (JGC) - Wednesday, 06 January 2010, 08:18 GMT
The gtk-doc documentation is installed because the tarball contains pre-generated documentation. As for the requirements of building in clean chroot: that's a policy for all packages built in our repositories. I don't like to add --disable flags for anything that could possibly be installed on a system when a package is built outside of a chroot.
Comment by Michael Witten (mfwitten) - Wednesday, 06 January 2010, 08:29 GMT
You don't have to use the --disable flag.

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.
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 11 February 2010, 07:01 GMT
any decision here?
Comment by Paul Mattal (paul) - Saturday, 06 March 2010, 21:42 GMT
It sounds like Jan's position is not to implement. I think I partially agree with Michael's #3 point, but it seems like Jan's decision here; it's a larger philosophical question if PKGBUILDs are valid if they don't build outside a clean chroot.

I'll close as "won't implement" on April 2010 bug day unless some new information or discourse appears.
Comment by Michael Witten (mfwitten) - Sunday, 07 March 2010, 06:27 GMT
> 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.

Loading...