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

[From: Ed Bartosh]

2009/11/5 Marius Vollmer <marius.vollmer at nokia.com>:
> ext Ed Bartosh <bartosh at gmail.com> writes:
>
>> 2009/11/5 Marius Vollmer <marius.vollmer at nokia.com>:
>>
>>> Then I propose to put maemo-optify into the sdk repo, add a dependency
>>> to it from build-essential and make a new SDK release.
>>>
>>> Whenever we need to update maemo-optify, we need to make a new
>>> rootstrap.
>>>
>> It would take a lot of time, I think.
>>
>> I have another idea. If it doesn't work proper way let's make a hack
>> in autobuilder.  Autobuilder will run maemo-optify-deb after the
>> build.
>
> Hmm, aren't we now trying to solve the problem of how to get
> maemo-optify into the build environment, not how to run it once it's
> there?
>
We were trying to solve the problem right way, but it looks like we
failed unless sbdmock author will accept the change or I'll decide to
fork sbdmock.

What I propose is to run maemo-optify-deb not on the build host inside
scratchbox, but on garage, after all packages have been already built.
I don't like this hack, but it looks like we run out of ideas.

> I.e., we have modified the debian-etch devkit to call maemo-optify-deb
> at the right time.  That modification to the devkit is 'stable'.  It is
> quite unlikely that we need to change the devkit again.
>
>> It will be run on garage, so anybody, who has root at garage can
>> update package there.
>> How does it sound?
>
> What would root at garage need to do, exactly?  Create new rootstraps?  Run
> apt-get install maemo-optify once in a while?  (Run pbuilder --update? :)
>
Run apt-get install maemo-optify on the garage when it's updated.

> If root at garage can do it, could the auto-builder do it as well?
autobuilder is run from non-root account and garage is pretty
important place. It's better to do it manually when needed.

-- 
BR,
Ed