[cairo-commit] pycairo ChangeLog, 1.38, 1.39 NEWS, 1.4,
1.5 RELEASING, 1.3, 1.4 README, 1.5, 1.6 Makefile.am, 1.8, 1.9
Steve Chaplin
commit at pdx.freedesktop.org
Tue Jan 11 23:09:07 PST 2005
Committed by: stevech1097
Update of /cvs/cairo/pycairo
In directory gabe:/tmp/cvs-serv26060
Modified Files:
ChangeLog NEWS RELEASING README Makefile.am
Log Message:
SC 2005/01/12
Index: ChangeLog
===================================================================
RCS file: /cvs/cairo/pycairo/ChangeLog,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- ChangeLog 12 Jan 2005 03:45:03 -0000 1.38
+++ ChangeLog 12 Jan 2005 07:09:05 -0000 1.39
@@ -1,3 +1,17 @@
+=== PyCairo snapshot 0.1.4 ===
+2005-01-12 Steve Chaplin <steve1097 at yahoo.com.au>
+
+ * configure.ac: Increment pycairo version to 0.1.4
+
+ * Makefile.am (EXTRA_DIST): add examples/svg2png.py and
+ examples/svgview.py
+
+ * NEWS: add notes for 0.1.4 snapshot
+
+ * README: add version numbers required for libsvg-cairo and pygtk
+
+ * RELEASING: move 'make distcheck' (step 2) to after step 5
+
2005-01-12 Steve Chaplin <steve1097 at yahoo.com.au>
* cairo/cairomodule.c (pycairo_pdf_surface_create): new wrapper
Index: NEWS
===================================================================
RCS file: /cvs/cairo/pycairo/NEWS,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- NEWS 28 Nov 2004 08:56:59 -0000 1.4
+++ NEWS 12 Jan 2005 07:09:05 -0000 1.5
@@ -1,3 +1,25 @@
+Snapshot 0.1.4 (2005-01-12 Steve Chaplin <steve1097 at yahoo.com.au>)
+===================================================================
+The PyCairo license has changed so that it is now dual-licensed under the LGPL
+and the MPL, the same as Cairo itself. For details see the COPYING file as
+well as COPYING-LGPL-2.1 and COPYING-MPL-1.1.
+
+New Cairo bindings:
+ cairo_pdf_surface_create
+ cairo_set_target_pdf
+
+New libsvg-cairo bindings:
+ svg_cairo_parse
+ svg_cairo_parse_buffer
+ svg_cairo_render
+ svg_cairo_get_size
+
+Other:
+ Added --without-pygtk configure option.
+ Renamed the PyCairo API _new() functions to _wrap() to allow _new() to
+ be used for python __new__ functions.
+
+
Snapshot 0.1.3 (2004-11-24 Carl Worth <cworth at cworth.org>)
==========================================================
After the recent server compromise we discarded all unsigned
Index: RELEASING
===================================================================
RCS file: /cvs/cairo/pycairo/RELEASING,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- RELEASING 24 Nov 2004 21:21:45 -0000 1.3
+++ RELEASING 12 Jan 2005 07:09:05 -0000 1.4
@@ -13,37 +13,32 @@
But it's probably good enough if "cvs -q update -Ad" generates no
output.
-2) Verify that the code passes "make distcheck"
-
- Running "make distcheck" should result in no warnings or
- errors and end with a message of the form:
-
- ===============================================
- pycairo-X.Y.Z archives ready for distribution:
- pycairo-X.Y.Z.tar.gz
- ===============================================
-
- (But the tar file isn't actually ready yet, as we still have
- some more steps to follow).
-
-3) Fill out an entry in the NEWS file
+2) Fill out an entry in the NEWS file
Sift through the information in ChangeLog since the last
snapshot. Summarize major changes briefly in a style similar
to other entries in NEWS.
-4) Increment pycairo_major/minor/micro_version in configure.ac
+3) Increment pycairo_major/minor/micro_version in configure.ac
[Should have some version guidelines here. Do we track the
cairo version at all? I don't know what the convention is for
python bindings of C libraries. ]
-5) Commit the changes to NEWS and configure.in
+4) Commit the changes to NEWS and configure.in
Don't forget to fill out the ChangeLog just like with any
other commit. It's especially important to mention the new
version number in the ChangeLog.
+5) Run "make distcheck" and verify that it gives in no warnings or errors and
+ ends with a message of the form:
+
+ ===============================================
+ pycairo-X.Y.Z archives ready for distribution:
+ pycairo-X.Y.Z.tar.gz
+ ===============================================
+
6) Run "make release-publish" which will perform the following steps
for you:
Index: README
===================================================================
RCS file: /cvs/cairo/pycairo/README,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- README 27 Dec 2004 23:54:57 -0000 1.5
+++ README 12 Jan 2005 07:09:05 -0000 1.6
@@ -1,13 +1,13 @@
PyCairo - Python bindings for Cairo
http://cairographics.org
-Dependencies
+Dependencies (with minimum versions required)
------------
- cairo 0.2.0 or higher
- Python 2.2 or higher
- libsvg-cairo optional
+ cairo 0.2.0
+ Python 2.2
+ libsvg-cairo 0.1.4, optional
Numeric Python optional
- PyGTK optional
+ PyGTK 1.99.16, optional
Compiling
---------
Index: Makefile.am
===================================================================
RCS file: /cvs/cairo/pycairo/Makefile.am,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- Makefile.am 30 Nov 2004 01:56:30 -0000 1.8
+++ Makefile.am 12 Jan 2005 07:09:05 -0000 1.9
@@ -12,6 +12,8 @@
examples/hering.py \
examples/lsystem.py \
examples/spiral.py \
+ examples/svg2png.py \
+ examples/svgview.py \
examples/text.py \
examples/warpedtext.py
More information about the cairo-commit
mailing list