Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Maemo: Developers

maemo-optify, autobuilder & /opt

  

 
First page Previous page 1 2 3 4 Next page Last page  View All Maemo developers RSS feed   Index | Next | Previous | View Threaded


bartosh at gmail

Nov 3, 2009, 3:44 AM

Post #51 of 88 (1336 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/3 Marius Vollmer <marius.vollmer [at] nokia>:
> ext Ed Bartosh <bartosh [at] gmail> writes:
>
>> 2009/11/3 Marius Vollmer <marius.vollmer [at] nokia>:
>>> ext Ed Bartosh <bartosh [at] gmail> writes:
>>>
>>>> We can hack dpkg-checkbuilddeps to unconditionally add maemo-optify to
>>>> the list of build dependencies.
>>>
>>> Ouch.  That's very desperate.
>>>
>> May be. But not as desperate as calling apt-get install from
>> dpkg-buildpackage :)
>
> Yeah, I have to agree, actually.
>
> Luckily, with apt-get upgrade being run during build, we don't need to
> change dpkg-checkbuilddeps and we can just update build-essential.
> (Unless I am missing something.  Do I?)
>
rootstrap is used as a build-essentials by sbdmock. The initial idea
was to put maemo-optify in there, but now we're trying to avoid that.

>>> Hmm, so is "apt-get upgrade" being executed at one point before calling
>>> dpkg-buildpackage?
>>
>> Yes it is.
>
> Cool, then that's our ticket to get maemo-optify into the build
> environment, I would say.
>
The only problem left is were to put 'apt-get install' :)

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


g+770 at cobb

Nov 3, 2009, 2:40 PM

Post #52 of 88 (1333 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
Dammit, why won't modest do proper quoting...
Marius (I think) wrote...
> ext Graham Cobb <g+770 [at] cobb> writes:
>
> > On Monday 02 November 2009 12:16:57 Ed Bartosh wrote:
> > > 2009/11/2 Marius Vollmer <marius.vollmer [at] nokia>:
> > > > 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

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


maemo at csipa

Nov 4, 2009, 4:04 AM

Post #53 of 88 (1323 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
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). For development purposes, of course one may want to
control exact packages and versions. When it comes to proper builds, however,
pbuilder et al are very handy as they allow you to check things compared to a
predefined, but pristine status (i.e. no whoopses because you manually
installed something in the SDK but forgot to add the dependency or have
fiddled with sources.list).

Regards,
Attila
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


jeremiah at jeremiahfoster

Nov 4, 2009, 5:56 AM

Post #54 of 88 (1323 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
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 [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 4, 2009, 6:05 AM

Post #55 of 88 (1327 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
Hi,

2009/11/2 Ed Bartosh <bartosh [at] gmail>:
> 2009/11/2 Marius Vollmer <marius.vollmer [at] nokia>:
>> [. Jussi, we would like to get a new debian-etch devkit for Maemo 5 with
>>  the attached patch.  Please advise how to best go about this.
>> ]
>>
>> ext Ed Bartosh <bartosh [at] gmail> writes:
>>
>>> I can also help with building devkit if needed.
>>
>> I didn't manage to get the devkit to compile (I didn't see a way to get
>> it to not install into / during build), but I have a patch anyway
>> (attached).
>>
> You can learn how to do it here:
> http://scratchbox.org/documentation/docbook/devkit.html
>
> Here you can get result of my build(patch attached):
> https://garage.maemo.org/builder/scratchbox-devkit-debian_1.0.16-1.optify_i386.deb
>
Has anybody tried this devkit? Does it work as expected? Should we deploy it?

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


g+770 at cobb

Nov 4, 2009, 6:37 AM

Post #56 of 88 (1322 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
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 [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 4, 2009, 7:00 AM

Post #57 of 88 (1319 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
ext Graham Cobb <g+770 [at] cobb> writes:

> 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!
> [...]
> 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.

I was close. :)

I have proposed to run apt-get install maemo-optify fmr within
dpkg-buildpackage, but that is quite clearly a very gross thing to do.
I have to admit that I pretty much have no dignity anymore when it comes
to kicking Maemo and Scratchbitch into behaving as they should... :/
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 4, 2009, 7:14 AM

Post #58 of 88 (1322 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
ext Ed Bartosh <bartosh [at] gmail> writes:

> Has anybody tried this devkit? Does it work as expected?

I tried it by building (slightly modified versions of) xournal, hermes,
and libliqbase, and everything went as expected.

The slight modification was "echo auto >debian/optify" to turn on
optification.

> Should we deploy it?

It has my vote.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 4, 2009, 7:17 AM

Post #59 of 88 (1320 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
ext Ed Bartosh <bartosh [at] gmail> writes:

>> I didn't manage to get the devkit to compile (I didn't see a way to get
>> it to not install into / during build), but I have a patch anyway
>> (attached).
>>
> You can learn how to do it here:
> http://scratchbox.org/documentation/docbook/devkit.html

Yeah, it tells me to chown /scratchbox/devkits/debian-etch to
myself... not very nice.

> I think we should ask him to build final variant, when everyone will
> be happy with it. Until that I can build it.

Ok, excellent.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 4, 2009, 7:25 AM

Post #60 of 88 (1332 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
ext Ed Bartosh <bartosh [at] gmail> writes:

> 2009/11/3 Marius Vollmer <marius.vollmer [at] nokia>:
>
>> Luckily, with apt-get upgrade being run during build, we don't need
>> to change dpkg-checkbuilddeps and we can just update build-essential.
>> (Unless I am missing something. Do I?)
>
> rootstrap is used as a build-essentials by sbdmock. The initial idea
> was to put maemo-optify in there, but now we're trying to avoid that.

Hmm, the rootstrap contains the "build-essential" package. If we put a
newer version of the build-essential package into extras-devel, then
that newer version will be installed by 'apt-get upgrade'.

If apt-get upgrade does indeed run during a build. I no longer think it
actually does. Checking the build log of maemo-optify certainly shows
no signs of running apt-get upgrade.

https://garage.maemo.org/builder/fremantle/maemo-optify_0.1/i386.root.log.OK.txt

>>>> Hmm, so is "apt-get upgrade" being executed at one point before calling
>>>> dpkg-buildpackage?
>>>
>>> Yes it is.
>>
>> Cool, then that's our ticket to get maemo-optify into the build
>> environment, I would say.
>>
> The only problem left is were to put 'apt-get install' :)

Which apt-get install? We just add a dependency on maemo-optify to
build-essential and apt-get upgrade does the rest. No?

I'll put a newer version of build-essential into extras-devel and see
what happens, fingers crossed.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 4, 2009, 9:52 AM

Post #61 of 88 (1317 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/4 Marius Vollmer <marius.vollmer [at] nokia>:
> ext Ed Bartosh <bartosh [at] gmail> writes:
>
>> Has anybody tried this devkit? Does it work as expected?
>
> I tried it by building (slightly modified versions of) xournal, hermes,
> and libliqbase, and everything went as expected.
>
Can you elaborate a bit? Is it implemented the way proposed by Andrew?

> The slight modification was "echo auto >debian/optify" to turn on
> optification.
So, it doesn't do anything by default, right?


--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


andrew at bleb

Nov 4, 2009, 9:54 AM

Post #62 of 88 (1316 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
On Wed, Nov 4, 2009 at 17:52, Ed Bartosh <bartosh [at] gmail> wrote:
> 2009/11/4 Marius Vollmer <marius.vollmer [at] nokia>:
>> ext Ed Bartosh <bartosh [at] gmail> writes:
>>
>>> Has anybody tried this devkit? Does it work as expected?
>>
>> I tried it by building (slightly modified versions of) xournal, hermes,
>> and libliqbase, and everything went as expected.
>>
> Can you elaborate a bit? Is it implemented the way proposed by Andrew?

"auto" for Hermes should do nothing, as it has entries in /opt (if, as
Ed asks, it does as I outlined).

Cheers,

Andrew

--
Andrew Flegg -- mailto:andrew [at] bleb | http://www.bleb.org/
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 4, 2009, 9:56 AM

Post #63 of 88 (1317 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/4 Marius Vollmer <marius.vollmer [at] nokia>:
> ext Ed Bartosh <bartosh [at] gmail> writes:
>
>> 2009/11/3 Marius Vollmer <marius.vollmer [at] nokia>:
>>
>>> Luckily, with apt-get upgrade being run during build, we don't need
>>> to change dpkg-checkbuilddeps and we can just update build-essential.
>>> (Unless I am missing something. Do I?)
>>
>> rootstrap is used as a build-essentials by sbdmock. The initial idea
>> was to put maemo-optify in there, but now we're trying to avoid that.
>
> Hmm, the rootstrap contains the "build-essential" package. If we put a
> newer version of the build-essential package into extras-devel, then
> that newer version will be installed by 'apt-get upgrade'.
>
> If apt-get upgrade does indeed run during a build. I no longer think it
> actually does. Checking the build log of maemo-optify certainly shows
> no signs of running apt-get upgrade.
>
I'm sorry. This is my faul. I thought you're asking about 'apt-get
update'. sbdmock doesn't run 'apt-get upgrade', it just unpacks
rootstrap and installs build deps.

> https://garage.maemo.org/builder/fremantle/maemo-optify_0.1/i386.root.log.OK.txt
>
>>>>> Hmm, so is "apt-get upgrade" being executed at one point before calling
>>>>> dpkg-buildpackage?
>>>>
>>>> Yes it is.
>>>
>>> Cool, then that's our ticket to get maemo-optify into the build
>>> environment, I would say.
>>>
>> The only problem left is were to put 'apt-get install' :)
>
> Which apt-get install? We just add a dependency on maemo-optify to
> build-essential and apt-get upgrade does the rest. No?
>
Sorry, but no.

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 4, 2009, 10:55 AM

Post #64 of 88 (1316 views)
Permalink
RE: maemo-optify, autobuilder & /opt [In reply to]
From: ext Ed Bartosh [bartosh [at] gmail]
>2009/11/4 Marius Vollmer <marius.vollmer [at] nokia>:
>> ext Ed Bartosh <bartosh [at] gmail> writes:
>>
>>> Has anybody tried this devkit? Does it work as expected?
>>
>> I tried it by building (slightly modified versions of) xournal, hermes,
>> and libliqbase, and everything went as expected.
>
> Can you elaborate a bit? Is it implemented the way proposed by Andrew?

For the devkit, "as expected" means to invoke "maemo-optify-deb --auto" at the right time.
Whatever maemo-optify-deb does is not under scrutiny yet.

>> The slight modification was "echo auto >debian/optify" to turn on
>> optification.
>
> So, it doesn't do anything by default, right?

Correct, the default mode for maemo-optify-deb --auto (when debian/optify
does not exist) is currently "none".
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 4, 2009, 11:24 PM

Post #65 of 88 (1302 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
ext Ed Bartosh <bartosh [at] gmail> writes:

>> If apt-get upgrade does indeed run during a build. I no longer think it
>> actually does. Checking the build log of maemo-optify certainly shows
>> no signs of running apt-get upgrade.
>
> I'm sorry. This is my faul. I thought you're asking about 'apt-get
> update'. sbdmock doesn't run 'apt-get upgrade', it just unpacks
> rootstrap and installs build deps.

Ahh, bummer. And you say there is little chance of fixing sbdmock to
run apt-get upgrade as well?

(I would argue that any buildbot should run apt-get upgrade before
building things, and possibly even apt-get dist-upgrade.)

Anyway, let's assume we can not fix our own buildbot.

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.

I don't think I am in the best positition to carry out this plan,
however. Any takers?
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 5, 2009, 2:06 AM

Post #66 of 88 (1297 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/5 Marius Vollmer <marius.vollmer [at] nokia>:
> ext Ed Bartosh <bartosh [at] gmail> writes:
>
>>> If apt-get upgrade does indeed run during a build.  I no longer think it
>>> actually does.  Checking the build log of maemo-optify certainly shows
>>> no signs of running apt-get upgrade.
>>
>> I'm sorry. This is my faul. I thought you're asking about 'apt-get
>> update'. sbdmock doesn't run 'apt-get upgrade', it just unpacks
>> rootstrap and installs build deps.
>
> Ahh, bummer.  And you say there is little chance of fixing sbdmock to
> run apt-get upgrade as well?
>
I'll try, but I doubt that changes will be accepted by sbdmock author.

> (I would argue that any buildbot should run apt-get upgrade before
> building things, and possibly even apt-get dist-upgrade.)
>
> Anyway, let's assume we can not fix our own buildbot.
>
> 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. It will be run
on garage, so anybody, who has root [at] garag can update package there.
How does it sound?

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 5, 2009, 2:09 AM

Post #67 of 88 (1291 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/5 Marius Vollmer <marius.vollmer [at] nokia>:
>
> (I would argue that any buildbot should run apt-get upgrade before
> building things, and possibly even apt-get dist-upgrade.)
>

Well, AFAIK each time SDK repo is updated they provided new rootstrap
with the latest packages.
At least it worked this way so far.

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


andrew at bleb

Nov 5, 2009, 2:44 AM

Post #68 of 88 (1288 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
On Thu, Nov 5, 2009 at 10:06, Ed Bartosh <bartosh [at] gmail> wrote:
>
> 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. It will be run
> on garage, so anybody, who has root [at] garag can update package there.
> How does it sound?

Isn't that partially where we started this discussion? :-)

Sounds like a fairly safe approach, although we'll have the community
patching (and maybe even pushing) to maemo-optify's git, it should
still be deployed in a carefully controlled manner.

Cheers,

Andrew

--
Andrew Flegg -- mailto:andrew [at] bleb | http://www.bleb.org/
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 5, 2009, 3:03 AM

Post #69 of 88 (1286 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/5 Andrew Flegg <andrew [at] bleb>:
> On Thu, Nov 5, 2009 at 10:06, Ed Bartosh <bartosh [at] gmail> wrote:
>>
>> 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. It will be run
>> on garage, so anybody, who has root [at] garag can update package there.
>> How does it sound?
>
> Isn't that partially where we started this discussion? :-)
>
> Sounds like a fairly safe approach, although we'll have the community
> patching (and maybe even pushing) to maemo-optify's git, it should
> still be deployed in a carefully controlled manner.
>

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 5, 2009, 3:04 AM

Post #70 of 88 (1289 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
ext Ed Bartosh <bartosh [at] gmail> writes:

> 2009/11/5 Marius Vollmer <marius.vollmer [at] nokia>:
>
>> 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?

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] garag can
> update package there.
> How does it sound?

What would root [at] garag need to do, exactly? Create new rootstraps? Run
apt-get install maemo-optify once in a while? (Run pbuilder --update? :)

If root [at] garag can do it, could the auto-builder do it as well?
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 5, 2009, 3:19 AM

Post #71 of 88 (1288 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/5 Ed Bartosh <bartosh [at] gmail>:
> 2009/11/5 Andrew Flegg <andrew [at] bleb>:
>> On Thu, Nov 5, 2009 at 10:06, Ed Bartosh <bartosh [at] gmail> wrote:
>>>
>>> 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. It will be run
>>> on garage, so anybody, who has root [at] garag can update package there.
>>> How does it sound?
>>
>> Isn't that partially where we started this discussion? :-)
>>
Exactly. We started discussion from this hack and I've tried to avoid
it. Unfortunately without much luck.
I'm still hoping that author of sbdmock will accept 'apt-get upgrade'
addition. If it happens we'll solve this properly.

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 5, 2009, 3:33 AM

Post #72 of 88 (1287 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/5 Marius Vollmer <marius.vollmer [at] nokia>:
> ext Ed Bartosh <bartosh [at] gmail> writes:
>
>> 2009/11/5 Marius Vollmer <marius.vollmer [at] nokia>:
>>
>>> 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] garag can
>> update package there.
>> How does it sound?
>
> What would root [at] garag 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] garag 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
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 6, 2009, 2:45 AM

Post #73 of 88 (1238 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/5 Ed Bartosh <bartosh [at] gmail>:
> 2009/11/5 Marius Vollmer <marius.vollmer [at] nokia>:
>> ext Ed Bartosh <bartosh [at] gmail> writes:
>>
>>> 2009/11/5 Marius Vollmer <marius.vollmer [at] nokia>:
>>>
>>>> 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've discussed this with sbdmock author and we decided to make small
change to sbdmock:
New configurable action will be introduced. This action will be
executed by sbdmock between unpacking rootstrap and installing
build-deps.

For Fremantle we can simply put 'apt-get install maemo-optify' in there.

I'll try to make this change on weekends and deploy new sbdmock and
devkit in production.

It would be nice If somebody could explain me what should I expect
from maemo-optify in the following cases:
- source package doesn't contain anything /opt specific, binary
package doesn't contain /opt
- source package doesn't contain debian/optify, binary package doesn't
contain /opt
- source package doesn't contain debian/optify, one binary package
doesn't contain /opt, another binary package does
- source package contains debian/optify, binary package contains /opt
- source package contains debian/optify, one binary package contains
/opt, another binary package doesn't
....

Thanks,

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


marius.vollmer at nokia

Nov 6, 2009, 5:00 AM

Post #74 of 88 (1229 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
ext Ed Bartosh <bartosh [at] gmail> writes:

> I've discussed this with sbdmock author and we decided to make small
> change to sbdmock: New configurable action will be introduced. This
> action will be executed by sbdmock between unpacking rootstrap and
> installing build-deps.
>
> For Fremantle we can simply put 'apt-get install maemo-optify' in there.
>
> I'll try to make this change on weekends and deploy new sbdmock and
> devkit in production.

Excellent, thanks!

> It would be nice If somebody could explain me what should I expect
> from maemo-optify in the following cases:

Maemo-optify can be invoked in a number of ways. I'll explain what
happens when the modified dpkg-buildpackage calls

maemo-optify-deb --auto

after running ./debian/rules build.

> - source package doesn't contain anything /opt specific, binary
> package doesn't contain /opt

Nothing will be done because debian/optify does not exist, and the
default mode is "none".

> - source package doesn't contain debian/optify, binary package doesn't
> contain /opt

Nothing will be done because debian/optify does not exist, and the
default mode is "none".

> - source package doesn't contain debian/optify, one binary package
> doesn't contain /opt, another binary package does

Nothing will be done because debian/optify does not exist, and the
default mode is "none".

> - source package contains debian/optify, binary package contains /opt

If debian/optify exists with the contents "auto", then the binary package
will be optified with the default heuristic.

The default heuristic will not do anything because it detects that the
binary package already contains a file or directory called "/opt" and it
will explicitly stop because of that.

> - source package contains debian/optify, one binary package contains
> /opt, another binary package doesn't

If debian/optify exists with the contents "auto", then the two packages
will be optified separately with the default heuristic.

The default heuristic will not do anything for the package that contains
"/opt", as described above.

For the package that does not contain "/opt", the default heuristic will
move ((files and (directories that have the same name as the package))
and are bigger than 2048 bytes) into /opt/maemo/.
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers


bartosh at gmail

Nov 6, 2009, 5:09 AM

Post #75 of 88 (1227 views)
Permalink
Re: maemo-optify, autobuilder & /opt [In reply to]
2009/11/6 Marius Vollmer <marius.vollmer [at] nokia>:
> ext Ed Bartosh <bartosh [at] gmail> writes:
>
>> I've discussed this with sbdmock author and we decided to make small
>> change to sbdmock: New configurable action will be introduced. This
>> action will be executed by sbdmock between unpacking rootstrap and
>> installing build-deps.
>>
>> For Fremantle we can simply put 'apt-get install maemo-optify' in there.
>>
>> I'll try to make this change on weekends and deploy new sbdmock and
>> devkit in production.
>
> Excellent, thanks!
>
>> It would be nice If somebody could explain me what should I expect
>> from maemo-optify in the following cases:
>
> Maemo-optify can be invoked in a number of ways.  I'll explain what
> happens when the modified dpkg-buildpackage calls
>
>    maemo-optify-deb --auto
Which is how it's used in modified dpkg-buildpackage, right?

> after running ./debian/rules build.
>
>> - source package doesn't contain anything /opt specific, binary
>>   package doesn't contain /opt
>
> Nothing will be done because debian/optify does not exist, and the
> default mode is "none".
>
So, after deployment nothing should change unless developers add
debian/optify to their packages, right?

When autobuilder expected to start to optify packages without
debian/optify in them?

--
BR,
Ed
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

First page Previous page 1 2 3 4 Next page Last page  View All Maemo developers RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.