Hello, I've made a Debian package for matplotlib and I've put it at: http://anakonda.altervista.org/debian/ I've read some specification for dependencies from http://bugs.debian.org/206691, this is my first package and so there are some (many?) things to fix. I think that the package may also include the api documentation generated with pydoc. -- /Vittorio Palmisano/ Home Page: http://redclay.altervista.org
Hi Vittorio, On Thu, Feb 12, 2004 at 11:14:19PM +0100, Vittorio Palmisano wrote: > I've made a Debian package for matplotlib and I've put it at: > http://anakonda.altervista.org/debian/ Thank you for the package. I had a short look at it. Some comments: 1) Somehow the python-matplotlib-0.50/build directory sneaked into your diff file. You should remove it from your sources and rebuilt your package. 2) You should check your package with lintian. Calling "lintian -i python-matplotlib_0.50-1_i386.changes" gives a lot of useful hints. I hope this helps, Jochen --=20 http://seehuhn.de/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jochen Voss ha scritto: > Hi Vittorio, > > > Thank you for the package. I had a short look at it. > Some comments: > > 1) Somehow the python-matplotlib-0.50/build directory sneaked > into your diff file. You should remove it from your sources > and rebuilt your package. > > 2) You should check your package with lintian. > Calling "lintian -i python-matplotlib_0.50-1_i386.changes" > gives a lot of useful hints. > > I hope this helps, > Jochen Ok, I have fixed this problems, now "lintian -i python-matplotlib_0.50-1_i386.changes" doesn't say nothing. I have updated the files on my repository, bye - -- /Vittorio Palmisano/ Home Page: http://redclay.altervista.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFALBMapT6bvDtyXOIRAotMAKCKjRsSkEqW1+ZghHsbPTPSkxiK5gCfcse1 nTVo7VRSpn42CrynvFDGNKY= =yfL1 -----END PGP SIGNATURE-----
>>>>> "Vittorio" == Vittorio Palmisano <re...@em...> writes: Vittorio> Ok, I have fixed this problems, now "lintian -i Vittorio> python-matplotlib_0.50-1_i386.changes" doesn't say Vittorio> nothing. I have updated the files on my repository, bye Hi Vittorio, thanks a bunch for doing this. A lot of people have asked for this, and there's been incremental progress here and there, but I'm glad to see you got everything done. I have a couple of favors to ask of you. The 0.50e release on the web site that you built against was an alpha release of the 0.50 series and a fair number of features, optimizations and bug fixes have been added since then. The current snapshot has been well tested and is in good shape - would you be willing to build the package one more time against it? http://nitace.bsd.uchicago.edu:8080/files/share/matplotlib-0.50m.tar.gz Now a couple of questions. I need to update the debian section of the web site. Could you write something explaining how a relatively novice debian user would go about getting python-matplotlib? Ie, what would they need to put in /etc/apt/sources.list, what commands would they need to issue from the shell, which of the backends are installed, etc... How do you handle the various backends, eg, gd, wx, pygtk and so on. Just to give you an idea of how much has changed since the 0.50e alpha release, in addition to the aforementioned bugs and optimizations, there are 2 new backends (paint and agg), a new Table class, and a new matlab function table to interface to it, and several examples. Note if you do rebuild, there is a src dir you'll want to include. On the topic of releases: David, my target date is early next week. Do you think you can get pypaint up by then? Thanks again, JDH
> > On the topic of releases: David, my target date is early next week. > Do you think you can get pypaint up by then? > > Thanks again, > JDH > Hi John, Sorry, last email wasn't to the list. From posts you've made, it looks like you've made some changes to pypaint. Do you want those committed before a pypaint release? Apart from that, I'm just tying up some loose ends, and then I'll be able to make the release - hopefully today, but maybe only Monday if you want your changes added. thanks, David Moore --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.580 / Virus Database: 367 - Release Date: 2004年02月06日
>>>>> "David" == David Moore <da...@sj...> writes: David> Sorry, last email wasn't to the list. From posts you've David> made, it looks like you've made some changes to pypaint. David> Do you want those committed before a pypaint release? David> Apart from that, I'm just tying up some loose ends, and David> then I'll be able to make the release - hopefully today, David> but maybe only Monday if you want your changes added. I don't have anything to add. I tried to get clipping working but didn't succeed. I think there are two problems 1) libart wants to paths to be counter clockwise for clipping to work (at least that's what I was told on the libart list), and I don't think all the path constructors insure this, eg draw_arc. 2) even when the paths are constructed properly, I think there is a problem in libart that causes clipping artifacts. So I think you'll be fine going with what you've got for now. It would be great to get clipping worked out in the long run, but I don't see any immediate solutions. On the font front: as I mentioned earlier, I ported font.c to agg and it's working. For high resolution images it works great. For small images (eg, dpi=60) the fonts look pretty bad. I think this is the same for paint and agg, at least in the comparisons I've looked at. This isn't surprising since the font code is the same. The two areas where small rasters come up are for web pages (which is where I assume your interests are) and embedding in GUI applications (which is important to me). Is this why you want to upgrade to freetype2? From my reading of some of the docs there, this is one thing that freetype2 does better. JDH
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Hunter ha scritto: > > I have a couple of favors to ask of you. The 0.50e release on the web > site that you built against was an alpha release of the 0.50 series > and a fair number of features, optimizations and bug fixes have been > added since then. The current snapshot has been well tested and is in > good shape - would you be willing to build the package one more time > against it? > > http://nitace.bsd.uchicago.edu:8080/files/share/matplotlib-0.50m.tar.gz > > Now a couple of questions. I need to update the debian section of the > web site. Could you write something explaining how a relatively > novice debian user would go about getting python-matplotlib? Ie, what > would they need to put in /etc/apt/sources.list, what commands would > they need to issue from the shell, which of the backends are > installed, etc... How do you handle the various backends, eg, gd, wx, > pygtk and so on. > > Just to give you an idea of how much has changed since the 0.50e alpha > release, in addition to the aforementioned bugs and optimizations, > there are 2 new backends (paint and agg), a new Table class, and a new > matlab function table to interface to it, and several examples. Note > if you do rebuild, there is a src dir you'll want to include. > I have rebuild the package with support for gtkgd. I have tried to build also the agg backend, but I can't find the source package for this library! I've found two version: one from http://antigrain.com and another from scipy cvs, but seems that there are some missing headers when I compile the backend. I have also packaged the gdmodule from http://newcenturycomputers.net/projects/gdmodule.html and the ttfquery module from http://sourceforge.net/projects/ttfquery/, all the debs are on http://anakonda.altervista.org/debian/ I can write some documentation about debian packages required, once I've tested them, but only for the next weekend, bye - -- /Vittorio Palmisano/ Home Page: http://redclay.altervista.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFALOhdpT6bvDtyXOIRAiQGAKDDQCrh0sELN09vI2dKYVfTKZ9H4ACgr8o2 ezklwMSi/Ke3zY5kK8DWwsI= =SX+C -----END PGP SIGNATURE-----
>>>>> "Vittorio" == Vittorio Palmisano <re...@em...> writes: Vittorio> I have rebuild the package with support for gtkgd. I Vittorio> have tried to build also the agg backend, but I can't Vittorio> find the source package for this library! I've found two Vittorio> version: one from http://antigrain.com and another from Vittorio> scipy cvs, but seems that there are some missing headers Vittorio> when I compile the backend. I have also packaged the Vittorio> gdmodule from Vittorio> http://newcenturycomputers.net/projects/gdmodule.html Vittorio> and the ttfquery module from Vittorio> http://sourceforge.net/projects/ttfquery/, all the debs Vittorio> are on http://anakonda.altervista.org/debian/ Wow, amazing work. You may want to look at the header of matplotlib.backends.backend_agg - this includes some install instructions, where to get agg, etc... However, that may not be necessary. I have built a new sdist that has all the prereqs for agg built in (fonttools, ttfquery, and agg2). You just have to set BUILD_AGG in setup.py and it should build, as long as your compiler is fairly recent. I'll leave it to you whether you want to use debian to get fontools and ttfquery, or use the ones included with matplotlib. I stripped all the fluff out of those 3 packages and with everything included the sdist is still under a megabyte. http://nitace.bsd.uchicago.edu:8080/files/share/matplotlib-0.50p.tar.gz I used this to build an all-in-one win32 installer, which will be nice because now win32 users with Numeric can make PS and PNG plots out of the box (zlib, libpng, freetype are statically built in). I'm going to upload the snapshot if you want to experiment with it. I should warn you though: I forgot yesterday that there is still a critical bug in wx that must be repaired. Thus there will be one more revision following this one. (Sorry) JDH