Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| ce859edc | 2016-03-11 20:28:21 | garbage collect CONFIGURE_SHARED | ||
| e76718f1 | 2015-04-21 18:51:24 | add some simple missing lzma WANTLIBs (crept in via libxml) | ||
| aa988913 | 2015-04-04 09:20:59 | Bump after the recent changes in packaging dbus and dconf. | ||
| 2382144b | 2015-03-16 18:07:34 | fold lib-only PFRAG.shared into PLIST, regen PLIST, and bump | ||
| 372cd2bc | 2014-09-13 16:36:53 | --disable-gtk-doc is handled by the infrastructure now. | ||
| 583834bd | 2013-10-26 08:02:57 | Fix dependencies and bump after the recent libsoup -gnome => -main merge. | ||
| 96ec38b0 | 2013-03-30 09:40:57 | Fix wantlib/depends. | ||
| 58f1a6f9 | 2013-03-21 08:45:11 | USE_LIBTOOL=Yes is the default now. | ||
| 9cd014a3 | 2013-03-11 11:02:49 | PERMIT_* / REGRESS->TEST sweep | ||
| ef5cb32a | 2012-09-21 14:48:05 | Stupid autohell is stupid... The situation is this: even when we --disable-gtk-doc, if gtk-doc is actually installed at configure stage, tools like gtkdoc-rebase will be picked up and run during the install target. That is bad because the gtk-doc package may have been removed by then, especially during dpb(1) bulks (we explicitely disable support for it so why should it stay...). So for now, let's add the following env to configure whenever we use --disable-gtk-doc, until a bettersolution is found... CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \ ac_cv_path_GTKDOC_REBASE="" \ ac_cv_path_GTKDOC_MKPDF="" |