Re: Re: bitpim binary modules breaks Gentoo QA policies
"Roger Binns" <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <073e01c64277$ca83bb10$3501a8c0@rogersqyvr14d3> |
> behind) without too much special effort, especially if I set higher > priorities for uploads with particularly important fixes. The vast majority of changes are to fix/update/add functionality for phones, especially newer ones. If that happens for a phone you don't have then it is irrelevant. If it happens for a phone you have then you'll desperately want the updates. We have had a very good track record of not introducing regressions. > The actual packages contain just BitPim, Do you cx_Freeze it in any way or just run from the .py files? I assume you compile the various modules inside BitPim such as native.usb and native.strings. Note also that must run python with -OO Let us know if there is anything we can put in the released packages that would make your life easier. From now on, instead of CVS tags the code will need to be grabbed from https://svn.sourceforge.net/svnroot/bitpim/releases/1.2.3 where 1.2.3 is the release name. BTW what is the Python version available on Debian? Can multiple versions be installed at the same time (Gentoo uses something called slots to accomplish that). > everything else it needs (including DSV, which I had to upload I'd dearly love to get rid of DSV as Python 2.3 introduced a library csv module. Sadly it doesn't handle unicode. > drawback of this is getting a slightly older version of wxPython than > BitPim wants because Debian's wxWidgets maintainer considers 2.6.2's > Gtk+ port too buggy to upload; however, it wasn't too hard to adjust > brewcompressedimage.py accordingly, and other code seems unaffected. Robin was away for a while. Now that he is back the pace of wxPython releases should resume including bug fixes. > Incidentally, ReleaseForge (releaseforge.sf.net) claims to make the > file release process a lot less painful; I've never had reason to try > it, though. ReleaseForge is a gui app using Qt. In that sense it is a marginal improvement over the web page interface supplied by SourceForge, but it just changes whose silly buttons you have to press. What I want is a command line app that takes simple parameters like the release version (creating it in SourceForge if it doesn't already exist) and the filename. It can guess the things like the format and processor. I did ask the author of ReleaseForge way back for this and he was too obsessed with the gui. It also wouldn't do things like creating a release if it didn't already exist - it would always create a release. Since I build the release files on multiple machines, I want to directly update SourceForge from each of them. I did find a Perl program at one point. Sadly it only allowed one file per release to be added. Roger ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642