IEEE 802.1X supplicant. This port does not support the wireless
WPA/WPA functionality yet, because it is missing in the OpenBSD
net80211 kernel implementation. Successfully tested with 802.1X on
ProCurve switches with OpenBSD running freeradius in the backend.
This port is based on work by Jussi Salzwedel, thanks!
ok aanriot@
Basically you can use this program to extract files from an ISO,
add files to an ISO, and create bootable ISOs.
It can open both ISO and NRG files but can only save as ISO.
From Giovanni Bechis <bigionews () snb ! it>
(And this time in the correct directory)
Basically you can use this program to extract files from an ISO,
add files to an ISO, and create bootable ISOs.
It can open both ISO and NRG files but can only save as ISO.
From Giovanni Bechis <bigionews () snb ! it>
Tweak WANTLIB (gmp only required when built with ghc).
Take maintainership.
Not that some regression tests fail. This will be fixed in the next
release.
- move libfaad from WANTLIB to LIB_DEPENDS and LIB_DEPEND
libfaad >= 1.0
- bump PKGNAME
libfaad move from WANTLIB to LIB_DEPENDS OK ajacoutot@ (MAINTAINER)
OK naddy@
- LIB_DEPENDS-faad libfaad >= 1.0
- bump PKGNAME-main and PKGNAME-${PLUGIN}
- remove unused PATCHLEVEL variable
- adjust WANTLIB-main and WANTLIB-gnome as per lib-depends-check
- sync patches with update-patches
OK naddy@
libfaad uses data types with machine dependent bit width in
prototypes in its public headers, but in the corresponding library
code, machine independent exact width data types are used.
solution:
change libfaad headers to use the same machine independent exact
width data types in the prototypes as in the library. since the
prototypes in the library headers are changed, users of libfaad
likely need to be modified to use exact width data types as well.
also:
- bump libfaad major version number
- update plugin code to use exact width data types for libfaad
interaction, as per new prototypes
- bump package version
- sync patches with update-patches
problem discovered by, solution discussed with, reviewed, tested
and OK naddy@
error.
Do the real erroring out through a fatal error in pkgpath.mk (and set
PKGPATH to something less confusing than an empty variable). This
solves PR 5510 for real.
