Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
2.13.24_1 06 Feb 2020 16:48:06 |
rene |
Remove the expired Zope 2.13 port and its now unused USES file.
Tested with: `make index` and `make -V USES` for all ports |
2.13.24_1 04 Jan 2020 10:08:31 |
antoine |
Deprecate parts of zope 2.13 stack
With hat: portmgr |
2.13.24_1 14 Aug 2019 12:25:09 |
mat |
Convert to UCL & cleanup pkg-message (categories w) |
2.13.24_1 20 Jun 2018 17:05:44 |
mat |
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight |
2.13.24_1 30 Nov 2017 15:50:34 |
mat |
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the (Only the first 15 lines of the commit message are shown above ) |
2.13.24_1 13 May 2016 13:00:39 |
amdmi3 |
- Do not install another garbage file
Approved by: portmgr blanket |
2.13.24_1 16 Apr 2016 10:06:17 |
rm |
sysutils/py-zdaemon: update to 4.1.0
And patch Zope to work with this zdaemon version
With hat: zope |
2.13.24 14 Apr 2016 07:51:26 |
rm |
www/zope213: update to 2.13.24 |
2.13.23 01 Apr 2016 14:33:58 |
mat |
Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.
With hat: portmgr
Sponsored by: Absolight |
2.13.23 04 Jul 2015 21:07:30 |
rm |
Update Zope to 2.13.23.
This update also includes:
- devel/py-Acquisition 4.0a1 -> 4.2.1
- devel/py-ExtensionClass 4.0a1 -> 4.2.1
- devel/py-Products.BTreeFolder2 2.13.4 -> 2.14.0
- devel/py-Products.ExternalMethod 2.13.0 -> 2.13.1
- mail/py-Products.MailHost 2.13.1 -> 2.13.2
- devel/py-Products.StandardCacheManagers 2.13.0 -> 2.13.1
- devel/py-zconfig 2.9.3 -> 3.0.4
- devel/py-zLOG 2.11.1 -> 2.11.2
Changes common across this ports: add LICENSE_FILE, add NO_ARCH, sort USE_PYTHON
MFH: 2015Q3 |
2.13.22_1 03 Jul 2015 21:11:16 |
rm |
www/zope213: make this port usable when installed from packages
Both ports users and package users now follow uniform procedure of creating
application instance.
Summary:
- Clean up port and remove `make instance` functionality that duplicates native
Zope tool functionality
- Standardize and ensure pkg-message instructions correctly set up Zope
- Make Portlint and Poudriere testport clean
- Set NO_ARCH
PR: 200040
Submitted by: Jason Unovitch <jason.unovitch@gmail.com>
MFH: 2015Q3 |
2.13.22 03 Jan 2015 08:41:21 |
mva |
- Convert USE_PYTHON to new USES in www/
With hat: python@ |
2.13.22 10 Mar 2014 18:01:09 |
bapt |
Convert www to USES=zip |
2.13.22 23 Feb 2014 18:51:27 |
rm |
Update zope to 2.13.22. Clean-up port.
This update include:
- devel/py-Products.ZCatalog: 2.13.23 -> 2.13.27
- devel/py-Products.ZCTextIndex: 2.13.4 -> 2.13.5 |
2.13.21 13 Jan 2014 21:00:04 |
rene |
Python cleanup:
- USE_PYTHON* = 2.X -> USE_PYTHON* = 2
- USE_PYTHON* = 2.X+ -> USE_PYTHON* = yes
Reviewed by: python (mva, rm)
Approved by: portmgr-lurkers (mat) |
2.13.21 20 Sep 2013 16:07:33 |
rm |
Update Zope to 2.13.21. This update also includes:
- security/py-AccessControl 2.13.12 -> 2.13.13
- textproc/py-zope.app.i18n 3.6.3 -> 3.6.4 |
2.13.19 20 Dec 2012 11:09:31 |
rm |
Update Zope to 2.13.19 along with required dependencies:
- devel/py-Products.PythonScripts: 2.13.0 -> 2.13.2
- devel/py-tempstorage: 2.12.1 -> 2.12.2
- security/py-AccessControl: 2.13.8 -> 2.13.12 |
2.13.16 13 Aug 2012 16:26:39 |
rm |
Import Zope 2.13.16 and update this release required dependencies:
- devel/py-DateTime: 3.0b3 -> 3.0
- security/py-AccessControl: 2.13.7 -> 2.13.8 |
2.13.15 26 Jun 2012 06:11:40 |
rm |
- update to 2.13.15
Changelog:
- Fix lock file cleanup if there's an error early in startup. |
2.13.14 03 Jun 2012 09:21:54 |
rm |
- update to 2.13.14
- remove files/patch-src-App_CacheManager.py. The problem
was solved upstream another way.
changelog:
http://pypi.python.org/pypi/Zope2/2.13.14#id1 |
2.13.13 21 Feb 2012 16:28:20 |
rm |
- update to 2.13.13
changes:
http://pypi.python.org/pypi/Zope2/2.13.13#id1 |
2.13.12 20 Jan 2012 11:03:54 |
rm |
- update to 2.13.12
Changes:
- Prevent a cross-site-scripting attack against the default standard error
message handling. (CVE-2010-1104).
- Use in operator instead of deprecated has_key method (which is not implemented
by OFS.ObjectManager). This fixes an issue with WebDAV requests for skin
objects.
VuXML entry will be added later this day. |
2.13.11 16 Jan 2012 10:33:34 |
rm |
- transfer maintainership for my zope-ports to zope@
- add them to virtual category `zope' |
2.13.11 14 Jan 2012 08:57:23 |
dougb |
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other. |
2.13.11 12 Dec 2011 17:35:44 |
rm |
- update to 2.13.11
Approved by: novel (mentor)
Feature safe: yes |
2.13.10 12 Dec 2011 09:27:55 |
rm |
Import Zope 2.13.
Much thanks to Wen Heping for actually adding all the needed ports
for this update and testing.
A lot of thanks goes to Doug Barton and Chris Rees for the help with
rc-script.
Submitted by: rm (myself, via github)
Approved by: novel, miwi (mentors)
Feature safe: yes |
2.11.8 12 Dec 2011 09:17:28 |
rm |
Forced commit to document the repocopy of www/zope211 to www/zope213.
PR: 162441
Submitted by: wen
Repocopied by: marcus
Approved by: novel, miwi (mentors)
Feature safe: yes |