[maemo-developers] maemo-optify, autobuilder & /opt
From: Marius Vollmer marius.vollmer at nokia.comDate: Tue Nov 3 10:32:54 EET 2009
- Previous message: maemo-optify, autobuilder & /opt
- Next message: maemo-optify, autobuilder & /opt
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 in general. If it does, we could just upload a newer version of build-essential into extras-devel that depends on maemo-optify. This is quite a correct way to go about this, I'd say. The mess results from the SDK repo not being identical to extras-devel (which I would call a bug in itself). To reduce the mess, we should probably first put a version of maemo-optify and the modified build-essential into the sdk repo and make a SDK release. We can then still put newer versions of maemo-optify into extras-devel. So, does the auto-builder run apt-get upgrade?
- Previous message: maemo-optify, autobuilder & /opt
- Next message: maemo-optify, autobuilder & /opt
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]