Commit graph

19 commits

Author SHA1 Message Date
gls
bd09e3b7ae Ooops, forgot to remove useless patch. 2011-04-12 06:19:48 +00:00
gls
8523786faf Update www/ap2-suphp to 0.7.1
From Peter Avalos in PR pkg/44762

pkgsrc changes:
- pkglint cleanups
- set LICENSE
- Add MESSAGE to mention the change in configuration file format.

Upstream changes:

suPHP 0.7.1 has been released.
This release fixes a bug causing problems with symbol links in the script path,
which was introduced with the 0.7.0 release.

suPHP 0.7.0 has been released.
With this release, several features that have been on the wish list for a long
time, have been realized:

* The module for Apache 1.3 only supported AddHandler for older releases.
This has been fixed: Now you can use AddType, too.
* PHP source highlighting: Files of MIME type application/x-httpd-php-source
will now be shown with source highlighting. Remember to set the suPHP_PHPPath
directive to enable this feature.
* suPHP_AddHandler and suPHP_RemoveHandler directives can now be used on per
vhost level, too.
* You can configure more than one docroot and use different variables (like
user name or home directory) within docroot and chroot settings.

Attention: The configuration syntax for suphp.conf has slightly changed with
this release. Be sure to read the documentation before upgrading, because
existing configuration files will not work without changing them.
2011-04-11 19:57:54 +00:00
joerg
e031855e4a Convert @exec/@unexec to @pkgdir or drop it. 2009-06-14 22:00:14 +00:00
obache
a6d81bf20d Update ap2-suphp to 0.6.3.
While here, add DESTDIR support and more adapt sample config file to default settings.

* Version 0.6.3 (30 March 2008)
- Fixed a possible race condition concerning the check for the
  right symlink owner.
- Added checks for the owner of the parent directories were added.

* Version 0.6.2 (19 November 2006)
- Made mod_suphp compatible with Apache 2.2
- Modified SmartPtr implementation (hopefully) fixing
  double free problem
- Fixed problem that caused the process to block
  when more than 4096 were written to stderr
- Implemented userdir support
- Fixed problem with PATH_INFO and PHP scripts

* Version 0.6.1 (26 November 2005)
- Changed usage of STL to gain better compatibility with old GCC versions
  (credits to Jeremy Chadwick for finding the relevant code)
- Fixed typos in mod_suphp.c (Apache 1.3)
  (credits to Johan Ekenberg for finding these typos)
- Fixed potential buffer overflow in function suphp_bucket_read() in
  src/apache2/mod_suphp.c
- Fix problems with scripts sending "Last-Modified" headers
- Extended autoconf script to look for an installation of APR
  and to use its includedir when building mod_suphp for Apache 2
- Added support for chroot() call before execution of script
2008-05-17 02:37:24 +00:00
rillig
ebcb0ce01e Resign from maintaining a lot of packages, so everyone is free to update
them at will.
2008-03-04 11:02:23 +00:00
rillig
105dd4b97c Some packages need lex and yacc. Patch by Aleksey Cheusov via
pkgsrc-users.
2007-11-17 12:04:11 +00:00
jlam
4390d56940 Make it easier to build and install packages "unprivileged", where
the owner of all installed files is a non-root user.  This change
affects most packages that require special users or groups by making
them use the specified unprivileged user and group instead.

(1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to
    unprivileged.mk.  These two variables are lists of other bmake
    variables that define package-specific users and groups.  Packages
    that have user-settable variables for users and groups, e.g. apache
    and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP},
    etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS
    so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER}
    and ${UNPRIVILEGED_GROUP}.

(2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS.
2007-07-04 20:54:31 +00:00
joerg
50590ddc44 Use versioned prefix and fix build with Apache 2. 2007-06-30 15:05:08 +00:00
schmonz
9fa51c07de Actually respect PKG_SYSCONFDIR. Now that devel/apr0/buildlink3.mk
sets BUILDLINK_INCDIRS.apr, remove custom CPPFLAGS. Use -e for the
SUBST_SED expression to mollify pkglint. Add APACHE_USER and VARBASE
to BUILD_DEFS. Don't try to remove lib/httpd on deinstall, as it
belongs to Apache. Bump PKGREVISION.
2007-05-29 22:17:19 +00:00
wiz
6e2c35c083 pkglint cleanup; update HOMEPAGE/MASTER_SITES.
From Sergey Svishchev in private mail.
2007-02-22 19:01:13 +00:00
xtraeme
431c865de4 * Use apache.mk to be compatible with the new apache22 pkg.
* Use PKG_APACHE_ACCEPTED.
2006-12-08 23:34:10 +00:00
rillig
b60d9cc047 The full pathname to apxs is provided by www/apache2/buildlink3.mk, so
use it. This fixes builds where ${LOCALBASE}/sbin is not in the PATH.
2006-06-25 09:08:01 +00:00
joerg
5911def816 Recursive revision bump / recommended bump for gettext ABI change. 2006-02-05 23:08:03 +00:00
wiz
768c589c29 Bump BUILDLINK_RECOMMENDED of textproc/expat to 2.0.0 because
of the shlib major bump.
PKGREVISION++ for the dependencies.
2006-01-24 07:31:52 +00:00
jlam
dc9594e09d Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.
2005-12-29 06:21:30 +00:00
rillig
579e977969 Ran "pkglint --autofix", which corrected some of the quoting issues in
CONFIGURE_ARGS.
2005-12-05 23:55:01 +00:00
joerg
0f6c3a43bd I don't understand why an Apache module depends on libtool to build a
dynamic version, but make it work on DragonFly anyway.

Fixes pkg/31155.

[distinfo already commited, CVS permission checks are weired]
2005-10-11 19:01:01 +00:00
joerg
76e5951b34 I don't understand why an Apache module depends on libtool to build a
dynamic version, but make it work on DragonFly anyway.

Fixes pkg/31155.
2005-10-11 18:58:44 +00:00
rillig
bb348049c8 Added ap2-suphp version 0.6.0.
The suPHP Apache module together with suPHP itself provides an easy way
to run PHP scripts with different users on the same server.

It provides security, because the PHP scripts are not run with the
rights of the webserver's user. In addition to that you probably won't
have to use PHP's "safe mode", which applies many restrictions on the
scripts.
2005-08-03 16:43:38 +00:00