Age | Commit message (Collapse) | Author | Files | Lines |
|
Bump PKGREVISION.
|
|
|
|
|
|
on some platforms that lacked shared library support in the past. The
list hasn't been maintained at all and the gain is very limited, so just
get rid of it.
|
|
(CVE-2009-0544), bump PKGREVISION
|
|
|
|
on packages that are affected by the switch from the openssl 0.9.7
branch to the 0.9.8 branch. ok jlam@
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
|
|
changes:
-added sha256 module
-Add PublicKey to Crypto.__all_
-bugfixes
|
|
|
|
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
|
ok'd a while back at pkgsrcCon by agc and wiz
|
|
|
|
Buildlink files: RECOMMENDED version changed to current version.
|
|
|
|
changes:
-bugfixes
-speed improvements, added benchmark tools
-support to RSA key objects for blinding and unblinding data
- * Renamed cansign(), canencrypt(), hasprivate(), to
can_sign, can_encrypt, has_private.
-* Many randpool changes.
|
|
|
|
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
Many changes since 0.1.3, compatibility is not provided, so this is
more or less a new pkg.
|
|
|
|
extension Makefile fragments, because they really don't have anything to
do with the buildlink[12] frameworks. Change all the Makefiles that use
application.buildlink.mk and extension.buildlink.mk to use application.mk
and extension.mk instead.
|
|
|
|
use canonical pkg name (pyX.Y-pkg-vers),
make passing of SSLBASE work
|
|
|
|
replace security/py-crypto (which isn't python-2.0-ready, and failed the
last dozen bulk builds for that reason).
Some help provided by Ty Sarna -- thanks!
|