[maemo-developers] maemo-optify, autobuilder & /opt

[From: Graham Cobb]

Dammit, why won't modest do proper quoting...
Marius (I think) wrote...
> ext Graham Cobb <g+770 at cobb.uk.net> writes:
>
> > On Monday 02 November 2009 12:16:57 Ed Bartosh wrote:
> > > 2009/11/2 Marius Vollmer <marius.vollmer at nokia.com>:
> > > > The buildbot would need to run "apt-get install maemo-optify" at the
> > > > right time.  Any idea of how to do that?
> > >
> > > Right way to do it is to include it into SDK rootstrap. Other ways I
> > > can think of look hackish.
> >
> > Can't we have the hacked dpkg-buildpackage add (if optification is turned on)
> > maemo-optify to the build dependencies?
>
> No, dpkg-buildpackage does not install build dependencies, it just
> checks whether they are satisfied.
>
> What the buildbot could do (and maybe does), is to run
>
>          apt-get upgrade
>
> at one point.  This is important to get the target into a current state

I don't object to the autobuilder running apt-get upgrade but I would object very strongly if dpkg-buildpackage were to do an upgrade!  Don't go messing around with my scratchbox development environment whenever i build something!  I have many strange repositories in my scratchbox sources.list at various times and I NEVER, EVER do an apt-get upgrade in my development scratchbox targets!  When I am developing, and particularly when I am 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 am not sure anyone was proposing that dpkg-buildpackage would do an upgrade but wanted to point out that it can't before anyone suggested it.

Graham