I did start a project to do that but i never gotr very far with it. But we really don't need it now -- sbdmock serves that need and has the advantage that it is the tool the autobuilder uses so you can use it to make sure you will build in the autolbuilder.
But I wasn't referring to real builds, I was referring to compiles during debugging and testing. I just wanted to make sure we can all use dpkg-buildpackage without it touching our apt environment. While we are about it, I don't think the SDK guys support people doing apt-get update. In the past we have been told they do not test that. -- Sent from Nokia Nseries mobile computer ----- Original message ----- > > On Nov 4, 2009, at 13:04, Attila Csipa wrote: > > > On Tuesday 03 November 2009 23:40:24 Graham Cobb wrote: > > > debugging, I need to be able to control exactly which versions of > > > various > > > libraries are being used for that particular build including, > > > sometimes, > > > old versions. And I often have different targets with different > > > library > > > versions deliberately installed. > > > > I'm not sure if it's possible/viable on scratchbox and the final > > SDK, but > > things like pbuilder make this easier (since they are in essence > > mini-autobuilders). > > pbuilder (Personal Builder)[0] and cowbuilder (Copy On Write Builder) > [1] both are extremely useful tools, I heartily recommend them. I > wonder if one day we might configure them for maemo somehow. > > Jeremiah > > 0. http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html > 1. http://wiki.debian.org/cowbuilder > _______________________________________________ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
