really want it.
This is still marked FORBIDDEN as there may be all sorts of horrible
incompatabilities with the perl5 in "base", but folks who are willing
to override this and experiment are welcome.
Consider this to be only partially supported. I'll happily commit
patches and fixes, but I don't want to answer too many questions.
Sorry!
bundles and replaces the old mx extensions for python.
I'll remove the old ports (devel/py-mx{DateTime,Proxy,Stack,Tools},
textproc/py-mxTextTools) after a short grace period to allow for testing
the new stuff.
Patch diddn't apply cleanly, not reflecting the current version.
Merged the changes.
Tested both standard package and "WITH_TK=yes"
PR: 25816
Submitted by: patrick@watson.org
myself (for the lack of children, whom I could've prohibited to
do it). Sorry.
Upgrade this port to:
. build against TCL-8.3 by default (controllable by TCL_VER)
. build with or without TK (controllable by NO_X)
. take over maintainership -- regretfully, Justin was
rather idle recently
. build the helpfiles once -- during the build stage --
not during the install stage
On a side note, I more and more resent the fact, that our TCL
8.3 is built with the -stubs. It just introduces more variables
without noticeable benefit. On FreeBSD shared libraries work
well...
I tested this with TCL-8.3 (with and without TK), and with
TCL-8.2 (without TK only). Please, test this more.
- Version numbering is negative, so PORTEPOCH must be bumped each time
- Distfile now match version number
- Original patch had wrong checksum
- avoid PORTEPOCH in installation path
PR: 22773
Submitted by: maintainer
latest version and switch to using a versioned distfile so it has a chance
to keep building, but mark BROKEN for now because the patches fail to
apply to the new version.
A detailed changelog is available at:
http://www.erlang.org/download/otp_src_R7B-2.readme
(NOTICE: there is an incompatibility with the previous version: see
OTP-3744)
Port note: I finally removed all the lib/ files from pkg-plist, and
switched to automatic plist generation because Erlang is so nice as to live
in its own subdirectory. Previous plist management involved far too many
%%HACKS%%, and untold hours of compilation/testing to get every combination
right.