--- pythoncad-0.1.37.orig/debian/rules +++ pythoncad-0.1.37/debian/rules @@ -0,0 +1,18 @@ +#!/usr/bin/make -f + +VERSION = $(shell head -n1 debian/changelog | sed -e 's/.*(//;s/-.*).*//') +TAG = $(shell head -n1 debian/changelog | sed -e 's/.*(//;s/-.*).*//;s/.*\./R/') + +%: + dh --buildsystem=python_distutils --with quilt $@ + +override_dh_auto_install: + dh_auto_install -- --install-scripts=/usr/share/pythoncad --install-lib=/usr/share/pythoncad + +override_dh_installchangelogs: + dh_installchangelogs NEWS + +get-orig-source: + git clone git://pythoncad.git.sourceforge.net/gitroot/pythoncad/pythoncad --branch ${TAG} ../pythoncad-${VERSION} + cd ../pythoncad-${VERSION} && rm -fr .git build dist Doc Mac_OS_X_Read_Me.txt pippo.txt *.pyc + tar czf ../pythoncad_${VERSION}.orig.tar.gz ../pythoncad-${VERSION} && rm -fr ../pythoncad-${VERSION} --- pythoncad-0.1.37.orig/debian/changelog +++ pythoncad-0.1.37/debian/changelog @@ -0,0 +1,244 @@ +pythoncad (0.1.37-1) unstable; urgency=low + + * New upstream release. + * debian/patches/as_reserved: + - Removed, applied upstream. + * debian/patches/desktop_file: + - Removed, applied upstream. + * debian/patches/image_path.patch: + - Do not look for gtkpycad.png in script current working directory, + use a relative path instead. + + -- Luca Falavigna Sat, 31 Oct 2009 11:20:35 +0100 + +pythoncad (0.1.36-1) unstable; urgency=low + + * New upstream release. + * Update my e-mail address. + * Add Python Applications Packaging Team to Uploaders. + * Add Vcs-* fields in source stanza. + * Switch to debhelper 7. + * Switch to quilt. + * Refresh debian/copyright, add missing informations. + * debian/patches/as_reserved: + - Do not use "as" as variable name (is a reserved word in Python 2.6), + this way byte-compilation does not fail (Closes: #521388). + * debian/patches/fails_to_exit: + - Removed, fixed with new upstream version. + * debian/patches/remove_unused_bindump: + - Removed, no longer needed. + * Remove python-dev from Build-Depends-Indep, use python instead. + * Depend on python-gobject. + * Depend on ${misc:Depends} in pythoncad binary stanza. + * Remove debian/dirs file, useless. + * Bump Standards-Version to 3.8.3, list of changes: + - Add debian/README.source file to document quilt usage. + * Add watch file. + + -- Luca Falavigna Sat, 29 Aug 2009 02:35:38 +0200 + +pythoncad (0.1.35-4) unstable; urgency=low + + * New Maintainer (Closes: #439159, #439160). + * debian/control: + - Build-dependencies adjusted as per Python policy. + - Bump Standards-Version to 3.8.0. + - Move Homepage field to Source stanza. + * debian/rules: + - Remove unneeded dh_* calls. + * Add debian/pyversions as per Python policy. + * Apply changes from Devid Filoni (Closes: #486208). + * debian/copyright: + - Add copyright holder, fix lintian warning. + - Make copyright valid UTF-8, fix lintian warning. + * debian/menu: + - Adhere to new menu policy. + * debian/patches/01_documentation.dpatch: + - Manage documentation added since 0.1.22-1 under dpatch. + + -- Luca Falavigna Wed, 02 Jul 2008 00:27:49 +0200 + +pythoncad (0.1.35-3) unstable; urgency=low + + * Orphaned + + -- Cédric Delfosse Wed, 22 Aug 2007 21:28:37 +0200 + +pythoncad (0.1.35-2) unstable; urgency=low + + * new patch 03_fails_to_exit: Fix for "pythoncad fails to exit" + (Closes: Bug#422422) Thanks to Edoardo Batini + + -- Cédric Delfosse Tue, 08 May 2007 21:12:44 +0200 + +pythoncad (0.1.35-1) unstable; urgency=low + + * New upstream release + * Fix "unable to save files due to incorrect attribute reference" + (Closes: Bug#420352) + + -- Cédric Delfosse Fri, 27 Apr 2007 23:05:27 +0200 + +pythoncad (0.1.33-2) unstable; urgency=low + + * Rebuild for python 2.4 (Closes: Bug#387334) + + -- Cédric Delfosse Fri, 6 Oct 2006 21:57:23 +0200 + +pythoncad (0.1.33-1) unstable; urgency=low + + * New upstream release + * Set debhelper compat mode to 5 + * Use python-support + + -- Cédric Delfosse Mon, 10 Jul 2006 22:40:15 +0200 + +pythoncad (0.1.31-1) unstable; urgency=low + + * New upstream release + * Add debhelper and dpatch to Build-Depends + * Set Standards-Version to 3.7.2 + + -- Cédric Delfosse Mon, 22 May 2006 20:32:33 +0200 + +pythoncad (0.1.29-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Wed, 15 Mar 2006 22:38:20 +0100 + +pythoncad (0.1.28-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Thu, 2 Feb 2006 22:10:45 +0100 + +pythoncad (0.1.26-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Fri, 11 Nov 2005 15:20:42 +0100 + +pythoncad (0.1.25-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Mon, 27 Jun 2005 21:37:05 +0200 + +pythoncad (0.1.24-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Sat, 14 May 2005 11:41:16 +0200 + +pythoncad (0.1.23-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Fri, 25 Mar 2005 19:22:55 +0100 + +pythoncad (0.1.22-1) unstable; urgency=low + + * New upstream release + * Add note in description about DWG and DXF file formats + (Closes: Bug#289354) + * Fix man page (Closes: Bug#289581) + * Add documentation from the web site (Closes: Bug#289580) + + -- Cédric Delfosse Mon, 31 Jan 2005 22:09:39 +0100 + +pythoncad (0.1.20-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Sat, 8 Jan 2005 15:05:26 +0100 + +pythoncad (0.1.19-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Mon, 22 Nov 2004 22:13:51 +0100 + +pythoncad (0.1.16-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Fri, 18 Jun 2004 22:26:56 +0200 + +pythoncad (0.1.14-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Mon, 31 May 2004 23:29:01 +0200 + +pythoncad (0.1.13-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Fri, 7 May 2004 19:48:14 +0200 + +pythoncad (0.1.12-1) unstable; urgency=low + + * New upstream release + * dpatch-ification + + -- Cédric Delfosse Sat, 6 Mar 2004 16:32:27 +0100 + +pythoncad (0.1.11-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Wed, 7 Jan 2004 22:04:52 +0100 + +pythoncad (0.1.10-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Tue, 11 Nov 2003 18:49:24 +0100 + +pythoncad (0.1.9-4) unstable; urgency=low + + * To really close FTBFS (Closes: Bug#213943): + * Build-Depends on python, python-dev (for dh_python) + * Depends on python2.3 and python2.3-gtk2 and patch source to work + with python 2.3 + + -- Cédric Delfosse Thu, 9 Oct 2003 22:47:49 +0200 + +pythoncad (0.1.9-3) unstable; urgency=low + + * Build-Depends on python2.2 and python2.2-dev (Closes: Bug#213943) + + -- Cédric Delfosse Sat, 4 Oct 2003 14:41:52 +0200 + +pythoncad (0.1.9-2) unstable; urgency=low + + * Depends on python2.2, because the package doesn't work with python2.3 + + -- Cédric Delfosse Sat, 9 Aug 2003 12:46:49 +0200 + +pythoncad (0.1.9-1) unstable; urgency=low + + * New upstream release + + -- Cédric Delfosse Wed, 30 Jul 2003 22:30:11 +0200 + +pythoncad (0.1.8-3) unstable; urgency=low + + * Add python-dev to Build-Depends-Indep (Closes: Bug#203026) + * Changed Depends field so that we are not too much depending on python2.2 + + -- Cédric Delfosse Sun, 27 Jul 2003 10:39:34 +0200 + +pythoncad (0.1.8-2) unstable; urgency=low + + * Add python2.2-xmlbase to Depends (Closes: Bug#202887) + + -- Cédric Delfosse Sat, 26 Jul 2003 18:12:18 +0200 + +pythoncad (0.1.8-1) unstable; urgency=low + + * Initial Release. + + -- Cédric Delfosse Tue, 1 Jul 2003 23:12:51 +0200 + --- pythoncad-0.1.37.orig/debian/copyright +++ pythoncad-0.1.37/debian/copyright @@ -0,0 +1,44 @@ +This package was debianized by: + + Cédric Delfosse on Tue, 1 Jul 2003 23:12:51 +0200 + +It was downloaded from: + + http://www.pythoncad.org + +Upstream Authors: + + Art Haas + Matteo Boscolo + +Copyright: + + Copyright © 2002-2007 Art Haas + Copyright © 2009 Matteo Boscolo + +License: + + This package is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This package is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this package; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + +On Debian systems, the complete text of the GNU General +Public License can be found in `/usr/share/common-licenses/GPL-2'. + +The Debian packaging is: + + Copyright © 2003-2007, Cédric Delfosse + Copyright © 2008-2009, Luca Falavigna + +and is licensed under the GPL, see above. + --- pythoncad-0.1.37.orig/debian/control +++ pythoncad-0.1.37/debian/control @@ -0,0 +1,20 @@ +Source: pythoncad +Section: graphics +Priority: optional +Maintainer: Luca Falavigna +Uploaders: Python Applications Packaging Team +Build-Depends: debhelper (>= 7.3.0), quilt (>= 0.46-7) +Build-Depends-Indep: python (>= 2.4), python-support (>= 0.5.3) +Standards-Version: 3.8.3 +Homepage: http://www.pythoncad.org +Vcs-Svn: svn://svn.debian.org/python-apps/packages/pythoncad/trunk/ +Vcs-Browser: http://svn.debian.org/viewsvn/python-apps/packages/pythoncad/trunk/ + +Package: pythoncad +Architecture: all +Depends: ${python:Depends}, ${misc:Depends}, python-gtk2 (>= 1.99.16), python-gobject +Description: Computer Aided Drafting (CAD) program + PythonCAD is a scriptable (with the Python language) and easy to use drafting + program. + . + Please note that this version still doesn't support DWG and DXF file formats. --- pythoncad-0.1.37.orig/debian/pyversions +++ pythoncad-0.1.37/debian/pyversions @@ -0,0 +1 @@ +2.4- --- pythoncad-0.1.37.orig/debian/compat +++ pythoncad-0.1.37/debian/compat @@ -0,0 +1 @@ +7 --- pythoncad-0.1.37.orig/debian/docs +++ pythoncad-0.1.37/debian/docs @@ -0,0 +1,2 @@ +README +debian/doc/* --- pythoncad-0.1.37.orig/debian/pythoncad.1 +++ pythoncad-0.1.37/debian/pythoncad.1 @@ -0,0 +1,21 @@ +.\" Hey, EMACS: -*- nroff -*- +.TH PYTHONCAD 1 "juillet 15, 2003" +.SH NAME +PythonCAD \- Computer Aided Drafting (CAD) program +.SH SYNOPSIS +.B pythoncad +.RI " files" ... +.SH DESCRIPTION +This manual page documents briefly the +.B pythoncad +commands. +This manual page was written for the Debian distribution +because the original program does not have a manual page. +Some basic usage informations about PythonCAD and its internal command +interpreter are available in /usr/share/doc/pythoncad/docs. +.PP +\fBpythoncad\fP is a scriptable (with the Python language) and easy to use drafting program. +Please note that this version still doesn't support DWG and DXF file formats. +.SH AUTHOR +This manual page was written by Cedric Delfosse , +for the Debian project (but may be used by others). --- pythoncad-0.1.37.orig/debian/manpages +++ pythoncad-0.1.37/debian/manpages @@ -0,0 +1 @@ +debian/pythoncad.1 --- pythoncad-0.1.37.orig/debian/menu +++ pythoncad-0.1.37/debian/menu @@ -0,0 +1,4 @@ +?package(pythoncad):needs="X11" section="Applications/Science/Engineering" \ + title="PythonCAD" command="/usr/bin/pythoncad" \ + icon="/usr/share/pixmaps/gtkpycad.xpm" + --- pythoncad-0.1.37.orig/debian/watch +++ pythoncad-0.1.37/debian/watch @@ -0,0 +1,5 @@ +version=3 +opts="uversionmangle=s/DS/0\./;s/-R/\./" \ +http://pythoncad.org/download.html \ + releases\/PythonCAD-(.*)\.tar\.gz + --- pythoncad-0.1.37.orig/debian/install +++ pythoncad-0.1.37/debian/install @@ -0,0 +1,3 @@ +gtkpycad.py usr/share/pythoncad +debian/gtkpycad.xpm usr/share/pixmaps +pythoncad.desktop usr/share/applications --- pythoncad-0.1.37.orig/debian/gtkpycad.xpm +++ pythoncad-0.1.37/debian/gtkpycad.xpm @@ -0,0 +1,329 @@ +/* XPM */ +static char * gtkpycad_xpm[] = { +"32 32 294 2", +" c None", +". c #424242", +"+ c #2A2A2A", +"@ c #323232", +"# c #3E3E3E", +"$ c #CBCBCB", +"% c #C1C0C0", +"& c #414141", +"* c #C3C3C3", +"= c #D2D2D2", +"- c #7C7C7C", +"; c #555555", +"> c #FFFFFF", +", c #A9B0B4", +"' c #5C737E", +") c #72797D", +"! c #CBDDE5", +"~ c #FBFCFC", +"{ c #666666", +"] c #DBDBDB", +"^ c #F7F5F4", +"/ c #226A8C", +"( c #000A10", +"_ c #001F2F", +": c #00263B", +"< c #D0DFE5", +"[ c #9B9B9B", +"} c #464647", +"| c #FBFBFB", +"1 c #707D85", +"2 c #012228", +"3 c #02597D", +"4 c #1F6182", +"5 c #EAEBEC", +"6 c #F1F0F2", +"7 c #646464", +"8 c #1E201B", +"9 c #625F65", +"0 c #666569", +"a c #4B5E32", +"b c #5E951C", +"c c #58891B", +"d c #2D3B1B", +"e c #4B583B", +"f c #465D2C", +"g c #384727", +"h c #302F30", +"i c #252525", +"j c #19151D", +"k c #5F971D", +"l c #558818", +"m c #548718", +"n c #6DAB24", +"o c #6CAA23", +"p c #6EAD24", +"q c #578A1C", +"r c #4E7A19", +"s c #70AF24", +"t c #3F5F19", +"u c #0D0A10", +"v c #2E4611", +"w c #71B125", +"x c #6DAC24", +"y c #6CA923", +"z c #6CAA24", +"A c #5D931E", +"B c #000001", +"C c #619821", +"D c #6BA823", +"E c #6EAC24", +"F c #6DAA24", +"G c #74B626", +"H c #000000", +"I c #5E9220", +"J c #426715", +"K c #4A7518", +"L c #69A622", +"M c #3F6415", +"N c #6BAA22", +"O c #15101A", +"P c #44671C", +"Q c #70B024", +"R c #53821B", +"S c #5B8F1E", +"T c #649D21", +"U c #273D0C", +"V c #598C1E", +"W c #476B1B", +"X c #5A9019", +"Y c #6BA723", +"Z c #6AA623", +"` c #68A422", +" . c #6AA723", +".. c #639B20", +"+. c #363636", +"@. c #5B5E57", +"#. c #527E19", +"$. c #67A322", +"%. c #6EAE24", +"&. c #5F961F", +"*. c #323A23", +"=. c #242525", +"-. c #734C47", +";. c #713E35", +">. c #273619", +",. c #2B4110", +"'. c #385712", +"). c #2F4A10", +"!. c #24390B", +"~. c #20230F", +"{. c #6D6E6F", +"]. c #95483D", +"^. c #0E1604", +"/. c #598C1D", +"(. c #76B926", +"_. c #3D5816", +":. c #030101", +"<. c #65433C", +"[. c #31420E", +"}. c #172307", +"|. c #082D10", +"1. c #000101", +"2. c #9A4639", +"3. c #90666C", +"4. c #565045", +"5. c #5D8B1B", +"6. c #22360B", +"7. c #000804", +"8. c #3A0C09", +"9. c #AB827E", +"0. c #686536", +"a. c #6AAA21", +"b. c #55841B", +"c. c #003A21", +"d. c #000B04", +"e. c #979092", +"f. c #60721F", +"g. c #6DAD24", +"h. c #73B325", +"i. c #284511", +"j. c #111100", +"k. c #171700", +"l. c #010100", +"m. c #4B4931", +"n. c #689620", +"o. c #6AA421", +"p. c #172708", +"q. c #1C1A1C", +"r. c #737300", +"s. c #B1B100", +"t. c #B6B600", +"u. c #A3A300", +"v. c #454500", +"w. c #474B1A", +"x. c #6FA823", +"y. c #6AA622", +"z. c #13461A", +"A. c #003D1C", +"B. c #C6C600", +"C. c #BFBF00", +"D. c #C0C008", +"E. c #9C9C08", +"F. c #C3C308", +"G. c #171707", +"H. c #79821F", +"I. c #6BA923", +"J. c #5E9821", +"K. c #05401D", +"L. c #057C31", +"M. c #101000", +"N. c #B0B000", +"O. c #ACAC08", +"P. c #000008", +"Q. c #3E3E08", +"R. c #828208", +"S. c #1C1A19", +"T. c #99B32A", +"U. c #6BAB23", +"V. c #1D551E", +"W. c #042912", +"X. c #1C1C1C", +"Y. c #BCBC1F", +"Z. c #D2D200", +"`. c #919111", +" + c #564F1E", +".+ c #8AB328", +"++ c #67A222", +"@+ c #507E1D", +"#+ c #0A1C11", +"$+ c #03401E", +"%+ c #A2A200", +"&+ c #363600", +"*+ c #303011", +"=+ c #645D25", +"-+ c #719521", +";+ c #6CAB24", +">+ c #3C6518", +",+ c #063719", +"'+ c #007E2F", +")+ c #00431F", +"!+ c #446A16", +"~+ c #454300", +"{+ c #C5C500", +"]+ c #3F3F00", +"^+ c #2A3919", +"/+ c #29271E", +"(+ c #9BAD29", +"_+ c #6BAA23", +":+ c #5F921E", +"<+ c #00341C", +"[+ c #016627", +"}+ c #003114", +"|+ c #3A5A17", +"1+ c #53871E", +"2+ c #043E1C", +"3+ c #003119", +"4+ c #406F1B", +"5+ c #030C03", +"6+ c #0F0F00", +"7+ c #848400", +"8+ c #989800", +"9+ c #383800", +"0+ c #050505", +"a+ c #3E4F28", +"b+ c #2E4712", +"c+ c #8D8F24", +"d+ c #6EA923", +"e+ c #72B024", +"f+ c #0F451B", +"g+ c #006427", +"h+ c #004B1F", +"i+ c #548D20", +"j+ c #72AF23", +"k+ c #71AF24", +"l+ c #70A523", +"m+ c #92A928", +"n+ c #8E9329", +"o+ c #000002", +"p+ c #0F1106", +"q+ c #111C05", +"r+ c #315E19", +"s+ c #102109", +"t+ c #161416", +"u+ c #23331B", +"v+ c #649921", +"w+ c #090507", +"x+ c #3C3817", +"y+ c #8FAE28", +"z+ c #6BAC24", +"A+ c #65A022", +"B+ c #42701A", +"C+ c #416F1A", +"D+ c #69A623", +"E+ c #6AAA23", +"F+ c #7E9D23", +"G+ c #555418", +"H+ c #484926", +"I+ c #6D821E", +"J+ c #68A922", +"K+ c #416615", +"L+ c #0B220C", +"M+ c #015F26", +"N+ c #035C25", +"O+ c #113D18", +"P+ c #485813", +"Q+ c #7B6C1C", +"R+ c #739420", +"S+ c #6FAE24", +"T+ c #6CAB23", +"U+ c #6DA523", +"V+ c #667D1D", +"W+ c #423E19", +"X+ c #26221D", +"Y+ c #798223", +"Z+ c #6DA623", +"`+ c #6FAF24", +" @ c #61981F", +".@ c #124319", +"+@ c #103713", +"@@ c #476315", +"#@ c #323421", +"$@ c #53512E", +"%@ c #929625", +"&@ c #6F8D20", +"*@ c #5B8C1D", +"=@ c #659C21", +"-@ c #62931F", +";@ c #789121", +">@ c #4E5117", +",@ c #575C1C", +"'@ c #5E8B1D", +")@ c #6BA722", +"!@ c #446113", +"~@ c #35371E", +" ", +" . ", +" + @ ", +" # $ % & * = - ", +" ; > , ' ) ! ~ > { ", +" ] ^ / ( _ : < > [ ", +" } | > 1 2 3 4 5 6 7 ", +" 8 9 0 a b c d e f g h ", +"i j k l m n o p q r s t u ", +" v w x y n z o n y x A B ", +" C n n D x n E F o o G H ", +" I n y J K L M z n n N O H H ", +" P Q E R S T U V x x W H H ", +" X p Y Z o ` .n .. H H H ", +" +.@.#.$.%.p p E &.*. H H H ", +" =.-.;.>.,.'.).!.~.{.H H H H H H ", +" ]. H ^./.(._. :.H H H H H ", +" <. [.H }.|. 1.H H H H ", +" 2.3. 4.5.6.7.H H H H H H H H ", +" 8.9. 0.a.b.c.d.H H H H H ", +" e. f.g.h.i.H H H H H H H H j.k.l. ", +" m.n.x o.p.q. H H H H r.s.t.u.v.H ", +" w.x.y.z.A. H H r.B.C.D.E.F.G. ", +" H.I.J.K.L. M.N.C.C.O.P.Q.R.H ", +" S.T.U.y.V.W. X.Y.D.O.H H Z.`.H ", +" +.+o n ++@+ #+$+H %+E.P.H H &+*+H ", +" =+-+;+n n >+ ,+'+)+!+~+{+]+Z.&+H H ^+ ", +" /+(+_+n :+<+[+}+|+1+2+3+4+y 5+6+7+8+9+H H 0+ a+b+ ", +" c+d+n e+f+g+h+i+E j+k+g.l+m+n+o+p+q+r+s+H t+ u+v+w+ ", +" x+y+z+n A+B+C+D+o o E+F+G+ H+I+J+D K+L+M+N+O+P+ ", +" Q+R+ .x S+S+n T+U+V+W+ X+Y+Z+`+ @.@+@@@#@ ", +" $@%@&@*@=@-@;@>@ ,@'@x )@!@~@ "}; --- pythoncad-0.1.37.orig/debian/doc-base +++ pythoncad-0.1.37/debian/doc-base @@ -0,0 +1,9 @@ +Document: pythoncad +Title: PythonCAD reference +Author: Art Haas +Abstract: This manual describes PythonCAD basic functions. +Section: Help/Books + +Format: HTML +Index: /usr/share/doc/pythoncad/usage.html +Files: /usr/share/doc/pythoncad/*.html --- pythoncad-0.1.37.orig/debian/README.source +++ pythoncad-0.1.37/debian/README.source @@ -0,0 +1,58 @@ +This package uses quilt to manage all modifications to the upstream +source. Changes are stored in the source package as diffs in +debian/patches and applied during the build. + +To configure quilt to use debian/patches instead of patches, you want +either to export QUILT_PATCHES=debian/patches in your environment +or use this snippet in your ~/.quiltrc: + + for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do + if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then + export QUILT_PATCHES=debian/patches + break + fi + done + +To get the fully patched source after unpacking the source package, cd to +the root level of the source package and run: + + quilt push -a + +The last patch listed in debian/patches/series will become the current +patch. + +To add a new set of changes, first run quilt push -a, and then run: + + quilt new + +where is a descriptive name for the patch, used as the filename in +debian/patches. Then, for every file that will be modified by this patch, +run: + + quilt add + +before editing those files. You must tell quilt with quilt add what files +will be part of the patch before making changes or quilt will not work +properly. After editing the files, run: + + quilt refresh + +to save the results as a patch. + +Alternately, if you already have an external patch and you just want to +add it to the build system, run quilt push -a and then: + + quilt import -P /path/to/patch + quilt push -a + +(add -p 0 to quilt import if needed). as above is the filename to +use in debian/patches. The last quilt push -a will apply the patch to +make sure it works properly. + +To remove an existing patch from the list of patches that will be applied, +run: + + quilt delete + +You may need to run quilt pop -a to unapply patches first before running +this command. --- pythoncad-0.1.37.orig/debian/links +++ pythoncad-0.1.37/debian/links @@ -0,0 +1 @@ +usr/share/pythoncad/gtkpycad.py usr/bin/pythoncad --- pythoncad-0.1.37.orig/debian/doc/commands.html +++ pythoncad-0.1.37/debian/doc/commands.html @@ -0,0 +1,348 @@ + + + + + +PythonCAD Command Interpreter + + + +

PythonCAD Command Interpreter Reference

+

+The table below gives the available commands in PythonCAD. An +example of a command set like those in the +keywords.py file is available at the bottom of the page. +The commands are listed in the second column of the table. The third +column in the table represents an internal command that gets run +when the command in the second column is seen. +

+

+It bears repeating that the ability of PythonCAD in dealing with these +commands is a new feature, and therefore you should expect to encounter +some undocumented features. As the development of PythonCAD +advances, the command interpreting abilities of the program should +stabilize and become more powerful with fewer surprises. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Command Interpreter (05/29/2003)
Command DescriptionDefault Name(s)Command Executed
Draw Angled Construction Lineacline,aclacline
Arc(Radius/Angle)arcarcc
Draw Construction Circle(Two Points)ccir2ccir2p
Draw Construction Circle(Point/Radius)ccirccircen
Chamfer Objectchamferchamfer
Draw Circle(Two Points)cir2cir2p
Draw Circle(Point/Radius)circircen
Draw Construction Line (Two Points)clcl
Close Drawing Windowcloseclose
Copy Objectcopycopy
Cut Objectcutcut
Delete Objectdelete, deldelete
Open Dimension Prefrences Windowdimprefdimpref
Fillet Objectfilletfillet
Horizontal Construction Linehcline, hclhcline
Draw Leader (Multi-Point)leader, leadleader
Mirror Objectmirror, mirmirror
Move Objectmove, mvmove
Move Object Horizontallymovehmoveh
Move Object Verticallymovevmovev
Open New Windownewnew
Paste Objectpastepaste
Draw Perpendicular Construction Linepclinepcline
Draw Pointpointpoint
Draw Polyline (Multi-Point)polyline, plinepolyline
Open Prefrences Menu Windowprefpref
Quit Applicationquitquit
Draw Rectangle (Two Points)rectangle, rectrect
Redraw Screen Objectsredrawredraw
Refresh Screen Objectsrefresh, rrefresh
Select all: arcssaasaa
Select all: angled construction linessaaclsaacl
Select all: circlessacsac
Select all: construction circlessaccsacc
Select all: construction linessaclsacl
Select all: horizontal construction linessahclsahcl
Select all: polylinessapsap
Select all: segmentssassas
Select all: vertical construction linessavclsavcl
Save Drawing as New Filenamesaveassaveas
Save Drawingsaves, svsaves
Draw Segment (Two Points)segment, seg, lsegment
Split Objectsplitsplit
Stretch Object (Two Points)strstr
Stretch Horizontalstrhstrh
Stretch Verticalstrvstrv
Draw Tangent Construction Linetcline, tcltcline
Input Texttexttext
Transfer to Current Layertransfertransfer
Draw Vertical Construction Linevcline, vclvcline
Zoom Defaultzoomd, zzoomd
Zoom Fitzoomf, zfzoomf
Zoom Inzoomi, zizoomi
Zoom Outzoomo, zozoomo
+

Example Command Set

+

+Defining a command set is essentially defining a Python dictionary. The +key is the command, and the value is the internal +command to execute when the user enters the command key. Here +is a commands set called mycommands. +

+
+mycommands = {
+	'foobar' : quit,
+	'foo' : segment,
+	'X' : quit,
+	'O' : opend
+}
+
+

+As the command interpreter is a new PythonCAD addition, it will undoubtedly +go through several iterations before it begins to stabilize. The command +set, internal command set, and means of selecting which dictionary to use +to try and interpret the commands are guaranteed to change. It is also +likely that commands may appear in one release, disappear in the next, then +reappear in the release after that, or that commands will change meanings. +

+ + --- pythoncad-0.1.37.orig/debian/doc/usage.html +++ pythoncad-0.1.37/debian/doc/usage.html @@ -0,0 +1,255 @@ + + + + + +PythonCAD Usage + + + +

+Usage Questions and Answers +

+

+A stated goal of the PythonCAD project is to produce an easy to use CAD +package. Still, questions will arise as to how to do some certain operation +in PythonCAD. This page will hopefully provide answers to these questions. +Keep in mind that the program is in its earliest form, so an answer stating +That cannot be done as the code for doing that has not yet been +written will be common. Over time, that answer should appear less +and less frequently, and some happy day in the future it will not appear +at all. If you are able to help develop the code and do so, that day arrives +sooner. +

+

How do I ...

+ +

+This list is by no means complete, and will be added to as various +new question arise. +

+

Entering Data

+

+If you are being prompted for a single value of something, like the +radius of a circle, just type it in the entry field below the drawing. +If you type in the value as an integer value (no decimal point), PythonCAD +will convert it to a float value if needed. If it does not do this then you +have found a bug. When PythonCAD wants you enter a point in the entry +area below the drawing, it will expect you to enter the point in parenthesis, +with the x and y coordinates separated by a comma. +So, if you wanted to enter a point at the location (0.0,0.0), just type it +in like that. You do not need quotes around the parentheses, nor around the +digits. +

+

+Some effort is made to evaluate what you enter, so if you enter the point +like this ((3.4 + 5.5), (2.3 + 3.2)), PythonCAD will create +a point at (8.9, 5.5). Entering any arbitrary expression into will probably +not work (yet), though at some point it is hoped that PythonCAD will be +able to handle really complex expressions. As Python itself can handle +the expressions, the weakness is in the PythonCAD code. +

+

Working with Layers

+

+PythonCAD is built around the idea that a drawing is simply a collection +of layers with various entities stored in each layer. There is no restriction +as to how many layers a drawing may have. All drawings will have at least +one layer, and, if you wanted to, you could put all the entities comprising +the drawing in that single layer. As drawings get more complex, though, it +will probably be clearer if you split up the entities between the layers. One +idea could be to place all the dimensions in a layer, the construction lines +and circles in another, etc. You will have to decide what works best for +your particular needs. +

+

+Nearly all the layer operations can be done through the layer display +on the side of the drawing. If you right-click a particular layer, a +pop-up menu will appear. This menu gives you the choices of renaming the +layer, hiding or showing it, and hiding or showing any layers that are +children of that layer. Eventually the code will allow you +to drag and drop the layers so you can re-parent them as needed. For now +the drag and drop functionality only allows you to re-order the layers +under a parent. That is, the children layers A-B-C can be +reordered to A-C-B. +

+

+If you add a new layer, the new layer becomes the active layer. +Any entities that are drawn will now be stored in this layer. If you want +to change which layer is active, just click on the layer that you want to +activate. When a drawing has multiple layers, the entities in the active +layer are drawn showing what color they have. Entities kept in the inactive +layers are all drawn the same color (currently a blue color). A future +release will allow you to choose the color for inactive layers, but for +now you have to stick with blue. +

+

+If you draw an object in one layer, and then decide you want to move it +to another layer, you can do that through the use of the Transfer +menu item in the Modify menu. After you invoke the menu item, +you can click on the objects that you want to pull into the current active +layer. Fillets and chamfers cannot be pulled from one layer to another just +yet; this problem should be rectified in an upcoming release. +

+

Printing and Plotting

+

+As of the seventeenth release, PythonCAD can now print! The program will +generate a PostScript file that can be sent to a printer or saved to +a file. The initial printing support has several know flaws, such as +not printing the dimension end-point markers like arrows or slashes. +Subsequent releases will fix these problems as well as enhance the +overall printing abilities of the program. +

+

+The strategy for printing support had always been to generate a file in +some format that did not depend on the interface, and PostScript has +filled that bill nicely. For people not using PostScript printers, there +are third party software packages like +Ghostscript that can convert +the PostScript output into other formats. +

+

Setting Object Attributes

+

+The current linetype, color, style, and line thickness are all set from +the Set submenu in the Draw menu. Depending on +which menu choice you make, a dialog box will appear and allow you to +set the value of whatever attribute you wish to change. +

+

Changing Object Attributes

+

+The ability to change an objects color, linetype, thickness, or style was +added in the second release. First, you must select the objects that you +want to change. Use the Select menu item in the Edit +menu to select the entities that will get modified. Next, go to the +Modify menu, and use one of the choices found in the +Change submenu. After clicking OK in whichever +dialog box that appears, the selected objects will now have the new attribute +values from your menu and dialog choice. +

+

+There is currently no easy way to identify which entities are selected, +and this deficiency will be rectified in an upcoming release. Also, after +changing the attribute of the selected entities, the selected entity list +is cleared. This behavior may or may not be a considered a feature, and +could change depending on user feedback. +

+

Adding new Linetypes/Styles/Dimension Styles

+

+There is no interface code written for doing this yet, so adding one of +these things means delving into the code. There should be either a simple +dialog box, or a sequence of dialogs, that will make it easy to do this +sort of work, but none of that has been written. Also, questions regarding +the saving and loading of these customized features will need answers, as +the initial release (and probably many following releases) do not have +any support for reading what would be a customization or preferences file. +

+

+For storing preferences, it is envisioned that there will be a global set +of preferences stored in some file, and a user-specific set of preferences +kept in each user's directory. If these files are written in Python code, +then they could be brought into the program via an import +statement, or the use of the imp module, though the decision +as to what these files will be written in, let alone their format, has +yet to be made. Feedback to the developers will determine what route to +pursue. Other file format options are things like XML or some home-grown +key/value text file. +

+

+Writing the preference files in Python does seem to present advantages +over other formats, as there would be no need to try and write some sort +of parser to read the file. Reading the file would be very quick, and any +errors could be caught by a simple try/except block. Other alternatives +could require more work for the importation of the data in the files. Still, +it may be simpler to write the information out in a format other +than Python, and that may be a deciding factor on just how to handle this +problem. +

+

+Update: Storing the preferences as files written in Python +has been implemented since the fifth release. This approach has utilized +the imp module to load the file and, as the preference file +is Python code, makes use of the Python interpreter to parse the file. This +approach has worked reasonably well, and has provided a good initial +implementation of storing and loading user preferences. At present editing +the global preference file is done with a text editor, and probably requires +root access as the file is hard-coded to reside in the /etc/pythoncad/ +directory. A user can copy this file to a $HOME/.pythoncad/ directory +and modify it to their own needs. It is planned that in some future revision +the file paths will be more adjustable, as well as be more suitable for +non-unix platforms. +

+

Dimensioning

+

+Dimensions are currently the most complex objects in PythonCAD. Any individual +dimension has a large number of attributes that can be set, such as line +and font color, dimension text position and formatting, and various properties +relating to the dimension lines themselves. Dimensions are also at a very +early stage in the code, so for all the things they can do, there are many +lines of code still needing to be written in order to exercise all the +dimension functionality that exists. +

+

+The fourth release of PythonCAD addressed many of the shortcomings in +the earlier releases. Angular dimensions can be created, displayed, and +saved, and linear dimensions will be displayed (they could be created but +wouldn't show up). The display of the dimension text is also improved, +and the interactive creation of dimensions now has some visual feedback +to indicate the dimension points and text location. There is still much +work to be added in making dimensions more flexible and editable, but +progress is being made, and the fourth release contains vastly improved +dimensioning capabilities. +

+

+General dimension properties can be set through the Preferences +menu item in the Dimension menu. Ideally, all drawing preferences +will be set though a single Preferences menu, and there will not +be one in both the Edit and Dimension menus. The +reason there are two menus now is that the author did not have a good way +to integrate dimensional preferences with the preference dialog that exists +in the Edit menu. It is clear that using a notebook widget with +lots of pages is not a good user interface design. The current +layout for selecting preferences needs to be completely reworked, as the +program will gain many more user-definable options in the coming releases. +Examples of good preference dialogs would be welcomed, as a clear, concise +means of setting preferences will probably borrow ideas from them. +

+

+For the initial releases, the easiest way to find out what a dimension can +do is poke around the dimension preference dialog, alter some of the +settings, then go dimension some objects in a drawing. Be advised that +PythonCAD will not add a dimension to a drawing if it is duplicating an +existing dimension. For example, if you have a drawing consisting of +a single line segment, this drawing can have at most one horizontal +dimension, one vertical dimension, and one linear dimension. You cannot +draw multiple identical dimensions between two points, as the second, third, +fourth, etc. dimension would just be repeating the information given in the +first dimension. This behavior is considered a feature, and it will take +a number of good reasons for changing this design decision. +

+

Commands

+

+The seventh release of PythonCAD shipped with the first iteration of +a command interpreter. The long-term goal with the command interpreter +is to make it possible to use PythonCAD to a great extent by just typing +commands in the entry box at the bottom of the screen. As this functionality +is new, it is quite limited in what it can do at the moment. Future releases +of PythonCAD will add more commands and enhance the usability of the +command interpreter. +

+

+Visit this page for a description of the available +commands in PythonCAD. +

+ + --- pythoncad-0.1.37.orig/debian/patches/series +++ pythoncad-0.1.37/debian/patches/series @@ -0,0 +1 @@ +image_path.patch --- pythoncad-0.1.37.orig/debian/patches/image_path.patch +++ pythoncad-0.1.37/debian/patches/image_path.patch @@ -0,0 +1,16 @@ +Description: Do not look for gtkpycad.png in script current working directory, use a relative path instead +Origin: Debian + +Index: pythoncad-0.1.37/PythonCAD/Interface/Gtk/gtkimage.py +=================================================================== +--- pythoncad-0.1.37.orig/PythonCAD/Interface/Gtk/gtkimage.py 2009-10-31 10:40:02.205649445 +0100 ++++ pythoncad-0.1.37/PythonCAD/Interface/Gtk/gtkimage.py 2009-10-31 10:40:50.185646015 +0100 +@@ -154,7 +154,7 @@ + self.__image = image + self.__window = gtk.Window() + self.__window.set_title("Untitled") +- self.__window.set_icon_from_file("gtkpycad.png") ++ self.__window.set_icon_from_file("/usr/share/pixmaps/gtkpycad.xpm") + self.__window.connect("destroy", self.__destroyEvent) + self.__window.connect("event", self.__windowEvent) + self.__window.connect("key_press_event", self.__keyPressEvent)