IABSD.fr/ports/net/libpcapnav
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
2382144b | 2015-03-16 18:07:34 | fold lib-only PFRAG.shared into PLIST, regen PLIST, and bump | |
|
570aa62a | 2015-01-18 03:12:39 | Drop remaining MD5/RMD160/SHA1 checksums. | |
 |
372cd2bc | 2014-09-13 16:36:53 | --disable-gtk-doc is handled by the infrastructure now. | |
|
58f1a6f9 | 2013-03-21 08:45:11 | USE_LIBTOOL=Yes is the default now. | |
 |
eae66e4a | 2013-03-11 11:35:43 | 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="" | |
 |
4949ec7c | 2011-09-21 17:20:56 | reset maintainership | |
 |
d1c6f808 | 2010-07-12 22:07:37 | use REVISION, checked with before/after make show=PKGNAMES (plus some extra-careful checking where there are complicated PSEUDO_FLAVORS). | |
 |
a8f72637 | 2008-02-14 21:36:27 | - update my e-mail address ok jasper@ | |
|
679dcb23 | 2007-09-26 20:14:37 | update libpcapnav to 0.8 and take over maintainership. ok sthen@ |