Fix the (still present in 7.16.3) libssh2 problems, at least so that
cURL works with the libssh2 0.17 in our ports tree.
PR: 114215 (the basic update)
Submitted by: pesho.petrov@gmail.com
port include:
- many bug fixes, a revised regression test suite.
- a new MLRISC code generator for the amd64.
- "lexgen" has been replaced by "ml-ulex".
- "ml-ulex", "ml-antlr" and "trace-debug-profile" are now part of
the default install.
Remove CONFLICTS with sml-nj. The sml-nj* ports now use a helper
script (installed as ${PREFIX}/bin/multiexec-wrapper) to resolve
conflicting executable names (such as sml, ml-lex, etc.).
Submitted by: Johannes 5 Joemann [MAINTAINER]
PR: ports/115826 (based on)
Submitted by: vittorio de martino <vdemart1 at tin.it>
Approved by: Eric van Gyzen <eric+fbports at vangyzen.net> (maintainer)
- Remove tack which was removed in 20070303 rollup patch
tack is now distributed as another tarball
- Remmove some files removed in 20070714 rollup patch
text-only alternative and embedded media objects. For example,
an HTML email with an alternative version in plain text and
with all the required images contained in the mail.
WWW: http://search.cpan.org/dist/Email-MIME-CreateHTML/
A Perl implementation of the Facebook API, working off of the
canonical Java and PHP implementations. By default it uses JSON::Any
to parse the response returned by Facebook's server. There is an option
to return the raw response in either XML or JSON.
WWW: http://search.cpan.org/dist/WWW-Facebook-API/
to a section of code, causing aliases to be made whereever Perl would
normally make copies instead. You can use this to improve efficiency
and readability, when compared to using references.
WWW: http://search.cpan.org/dist/Data-Alias/
File::Slurp::WithinPolicy. The purpose is to allow systems administrators to
define locations and restrictions for applications' file I/O and give app
developers a policy to follow. Note that the module doesn't ENFORCE the
policy - application developers can choose to ignore it
(and systems administrators can choose not to install their applications
if they do!).
You may control which policy gets applied by creating a File::Policy::Config
module with an IMPLEMENTATION constant. You may write your own policy as a
module within the File::Policy:: namespace.
By default (if no File::Policy::Config is present), the File::Policy::Default
policy gets applied which doesn't impose any restrictions and provides
reasonable default locations for temporary and log files.
WWW: http://search.cpan.org/dist/File-Policy/
