Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. 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#56594 - [libmicrohttpd] 0.9.57 unneeded build of library examples

Attached to Project: Community Packages
Opened by Evgeny Grin (Karlson2k) - Tuesday, 05 December 2017, 14:54 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 05 December 2017, 21:35 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

libmicrohttpd by default build examples during 'make'.
However, those examples are not installed anywhere and provided only to illustrate usage of libmicrohttpd.
Build of examples could be disabled by 'configure' flag to speedup package building.

Patch is attached.
   0005-libmicrohttpd-disable-bu... (0.7 KiB)
This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 05 December 2017, 21:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  in svn trunk
Comment by Eli Schwartz (eschwartz) - Tuesday, 05 December 2017, 15:40 GMT
  • Field changed: Task Type (Bug Report → General Gripe)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Christian Hesse (eworm)
Hmm, maybe the upstream build system should not build these by default then. They should probably be built by a separate "examples" target which the install target would not depend on.
Comment by Evgeny Grin (Karlson2k) - Tuesday, 05 December 2017, 15:45 GMT
Separate make target will be hard to find for MHD users.
Excluding this special target from "make install", but not from "make all" is a tricky and not worth time investment.

'configure' flag is something that is very easy to use.
Comment by Eli Schwartz (eschwartz) - Tuesday, 05 December 2017, 15:46 GMT
Also when proposing general cleanup of the PKGBUILD, you don't need to file each change as a separate bugreport.

 FS#56590   FS#56591   FS#56592   FS#56593   FS#56594   FS#56595  could all be one ticket...
Comment by Evgeny Grin (Karlson2k) - Tuesday, 05 December 2017, 16:05 GMT
Right, all could be combined.
However, this way is simpler to manage tickets: some could be rejected, some could be accepted.

Loading...