cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

import py-addons-0.6

Browse Source 
Separating concerns into different objects makes it easier
to write reusable and separately-testable components.  The AddOns
package (``peak.util.addons``) lets you manage concerns using
``AddOn`` classes.

input, ok fgs@
This commit is contained in:
martynas 2009-04-05 00:45:48 +00:00
parent 840a859b74
commit 36b3a0c4e4
4 changed files with 67 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
devel/py-addons/Makefile Normal file
View File

@ -0,0 +1,38 @@
# $OpenBSD: Makefile,v 1.1.1.1 2009/04/05 00:45:48 martynas Exp $
COMMENT = extend python objects with addons
MODPY_EGG_VERSION = 0.6
DISTNAME = AddOns-${MODPY_EGG_VERSION}
PKGNAME = py-addons-${MODPY_EGG_VERSION}
CATEGORIES = devel
HOMEPAGE = http://pypi.python.org/pypi/AddOns
MAINTAINER = Martynas Venckus <martynas@openbsd.org>
# PSF
PERMIT_PACKAGE_CDROM = Yes
PERMIT_PACKAGE_FTP = Yes
PERMIT_DISTFILES_CDROM = Yes
PERMIT_DISTFILES_FTP = Yes
MASTER_SITES = ${MASTER_SITE_PYPI:=A/AddOns/}
EXTRACT_SUFX = .zip
UNZIP = unzip -a
MODULES = lang/python
RUN_DEPENDS = ::devel/py-decoratortools
BUILD_DEPENDS = ${RUN_DEPENDS}
MODPY_SETUPTOOLS = Yes
post-extract:
@find ${WRKSRC} -type f -exec chmod 644 {} \;
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/py-addons
${INSTALL_DATA} ${WRKSRC}/README.txt ${PREFIX}/share/doc/py-addons/
.include <bsd.port.mk>

5
devel/py-addons/distinfo Normal file
View File

@ -0,0 +1,5 @@
MD5 (AddOns-0.6.zip) = zOO5jjCu7n6Rhkmhi6j4tw==
RMD160 (AddOns-0.6.zip) = mkyWMjAutNzJLWzqiyjwwgFBZ/g=
SHA1 (AddOns-0.6.zip) = tLQLMjbocOc+9WH5jHspHIxt8ME=
SHA256 (AddOns-0.6.zip) = ZZmc6ZqvS6Jjvj0l8Tjqsr1HGnTF9qHIAiYpoUnnCZo=
SIZE (AddOns-0.6.zip) = 33893

11
devel/py-addons/pkg/DESCR Normal file
View File

@ -0,0 +1,11 @@
In any sufficiently-sized application or framework, it's common to
end up lumping a lot of different concerns into the same class.
For example, you may have business logic, persistence code, and UI
all jammed into a single class. Attribute and method names for all
sorts of different operations get shoved into a single namespace
-- even when using mixin classes.
Separating concerns into different objects, however, makes it easier
to write reusable and separately-testable components. The AddOns
package (``peak.util.addons``) lets you manage concerns using
``AddOn`` classes.

13
devel/py-addons/pkg/PLIST Normal file
View File

@ -0,0 +1,13 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2009/04/05 00:45:48 martynas Exp $
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}-nspkg.pth
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/PKG-INFO
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/SOURCES.txt
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/dependency_links.txt
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/namespace_packages.txt
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/requires.txt
lib/python${MODPY_VERSION}/site-packages/AddOns-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/top_level.txt
lib/python${MODPY_VERSION}/site-packages/peak/util/addons.py
lib/python${MODPY_VERSION}/site-packages/peak/util/addons.pyc
share/doc/py-addons/
share/doc/py-addons/README.txt