On 2013-09-23 17:49 +0200, Martin Owens wrote:
I'd also like something about how to use the multiple packages we have in the trunk ppa system to narrow down a problem. I think SUV has this magic already, allowing other bug hunters and devels to know how to set that up would be very useful.
Not really, MARTIN. I use a not-so proper (aka proprietary) OS as main platform, and have no magic at hand to share on how to use multiple packages from the inkscape-trunk PPA on Ubuntu for bug triage.
My own usage of PPAs is limited to keeping inkscape-trunk more or less up-to-date in two Ubuntu VMs (12.04, 13.04), but in those VMs I never downgrade or test with multiple versions other than the current latest one available from the PPA.
Archived builds mentioned in my comments in the bug tracker are all locally compiled and - per branch - installed into a custom $PREFIX. For the most part these builds are done on OS X, and and only a few in a Ubuntu 12.10 VM. My "archiving" method is very crude, and limited to the main inkscape binary (caveat: within the same prefix, the shared resources are always those from HEAD, even if I run an "archived" binary). Basic step is to rename the installed binary before pulling/updating:
$ mv $PREFIX/bin/inkscape{,-`bzr revno`} $ bzr pull $ # out-of-src build [1] $ (cd build; make && make install)
I'm sure there are better and more sophisticated ways to maintain a local archive of older builds - for me, it serves its purpose.
Regards, V
[1] http://article.gmane.org/gmane.comp.graphics.inkscape.devel/37448