Commit graph

12 commits

Author SHA1 Message Date
wiz
7eeb51b534 Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
2014-05-29 23:35:13 +00:00
jperkin
45bc40abb4 Remove example rc.d scripts from PLISTs.
These are now handled dynamically if INIT_SYSTEM is set to "rc.d", or
ignored otherwise.
2014-03-11 14:04:57 +00:00
asau
e4aa5f886a One more file installed on FreeBSD. 2013-12-17 07:07:22 +00:00
is
4ae4df7c4c Update to 1.97.
Among others, this changes using crypto:sha() to crypto:hash() for Erlang
that is new enough.

Bugfixes in pam, sendfile, generation of mime_types.erl
Other changes in the area of Webdav, sendfile, embedded mode, rebar
support, ssl options.
Optimization in ssi code.
2013-11-13 15:59:22 +00:00
fhajny
202121c2a0 Update yaws to 1.96.
Too many changes, see website for changelog:

http://yaws.hyber.org/
2013-07-19 09:53:34 +00:00
wiz
d2ca14a3f1 Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.
2013-05-31 12:39:57 +00:00
asau
5eae6a18a3 Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. 2012-10-28 06:30:00 +00:00
wiz
8b5d49eb78 Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
2012-10-03 21:53:53 +00:00
marino
50e463e5f8 www/yaws: Fix PLIST for DragonFly 2012-05-21 15:51:27 +00:00
dholland
b6bebb67db Add missing PAM buildlink, and tell configure script where to find it.
Otherwise only builds with native PAM.
2012-03-20 16:25:51 +00:00
hans
906ba7c681 Use ${RM} -f to avoid failure if no files are found to be removed. 2012-02-02 09:48:42 +00:00
cheusov
1941d84d6a Import from wip/yaws requested and tested under
DragonflyBSD by Andrey N. Oktyabski.

Yaws is a HTTP high perfomance 1.1 webserver particularly well suited for
dynamic-content webapplications. Two separate modes of operations are
supported:
 * Standalone mode where Yaws runs as a regular webserver daemon.
   This is the default mode.
 * Embedded mode where Yaws runs as an embedded webserver in another
   erlang application.

Yaws is entirely written in Erlang furthermore it is a multithreaded
webserver
where one Erlang light weight process is used to handle each client.

The main advantages of yaws compared to other Web technologies are
performance
and elegance. The performance comes from the underlying Erlang system and
its
ability to handle concurrent processes in an efficent way. Its elegance
comes
from Erlang as well. Web applications dont have to be written in ugly adhoc
languages.
2011-08-26 13:46:43 +00:00