rpms/python-peak-util-addons/EL-5 import.log, NONE, 1.1 python-peak-util-addons.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
Luke Macken
lmacken at fedoraproject.org
Thu Sep 11 08:47:12 UTC 2008
- Previous message (by thread): rpms/ikiwiki/devel .cvsignore, 1.8, 1.9 ikiwiki.spec, 1.7, 1.8 import.log, 1.7, 1.8 sources, 1.8, 1.9
- Next message (by thread): rpms/python-peak-util-addons/EL-4 import.log, NONE, 1.1 python-peak-util-addons.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: lmacken
Update of /cvs/pkgs/rpms/python-peak-util-addons/EL-5
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv19609/EL-5
Modified Files:
.cvsignore sources
Added Files:
import.log python-peak-util-addons.spec
Log Message:
Initial import of python-peak-util-addons
--- NEW FILE import.log ---
python-peak-util-addons-0_6-1_fc9:EL-5:python-peak-util-addons-0.6-1.fc9.src.rpm:1221122793
--- NEW FILE python-peak-util-addons.spec ---
%{!?python_sitelib: %define python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")}
%define packagename AddOns
Name: python-peak-util-addons
Version: 0.6
Release: 1%{?dist}
Summary: Dynamically extend other objects with AddOns
Group: Development/Languages
License: Python or ZPLv2.1
URL: http://pypi.python.org/pypi/AddOns
Source0: http://pypi.python.org/packages/source/A/%{packagename}/%{packagename}-%{version}.zip
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: python-devel
BuildRequires: python-setuptools-devel
Requires: python-decoratortools >= 1.5
%description
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.
%prep
%setup -q -n %{packagename}-%{version}
%build
%{__python} setup.py build
%install
rm -rf %{buildroot}
%{__python} setup.py install --skip-build --root %{buildroot}
%clean
rm -rf %{buildroot}
%files
%defattr(-,root,root,-)
%doc README.txt
%{python_sitelib}/*
%changelog
* Sun Aug 12 2008 Luke Macken <lmacken at redhat.com> - 0.6-1
- Initial package for Fedora
Index: .cvsignore
===================================================================
RCS file: /cvs/pkgs/rpms/python-peak-util-addons/EL-5/.cvsignore,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- .cvsignore 11 Sep 2008 05:00:48 -0000 1.1
+++ .cvsignore 11 Sep 2008 08:46:41 -0000 1.2
@@ -0,0 +1 @@
+AddOns-0.6.zip
Index: sources
===================================================================
RCS file: /cvs/pkgs/rpms/python-peak-util-addons/EL-5/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sources 11 Sep 2008 05:00:48 -0000 1.1
+++ sources 11 Sep 2008 08:46:41 -0000 1.2
@@ -0,0 +1 @@
+cce3b98e30aeee7e918649a18ba8f8b7 AddOns-0.6.zip
- Previous message (by thread): rpms/ikiwiki/devel .cvsignore, 1.8, 1.9 ikiwiki.spec, 1.7, 1.8 import.log, 1.7, 1.8 sources, 1.8, 1.9
- Next message (by thread): rpms/python-peak-util-addons/EL-4 import.log, NONE, 1.1 python-peak-util-addons.spec, NONE, 1.1 .cvsignore, 1.1, 1.2 sources, 1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the fedora-extras-commits
mailing list