On Mon, Jan 4, 2010 at 11:16 AM, Marius Vollmer <[email protected]> wrote: > ext Anderson Lizardo <[email protected]> writes: > >> Is maemo-optify-deb run on autobuilder inside the scratchbox target >> and after all dependencies have been installed? > > Yes. It is run after the package archives have been built and after > pymaemo-optify has done its thing. So maybe it is best just to look for > the effect that pymaemo-optify has. Maybe pymaemo-optify could even > just "echo none >debian/optify"... I'll have to have a closer look at > how pymaemo-optify actually works...
pymaemo-optify currently works on run-time (using the bind mount trick), so it does not modify any packages. Only python2.5 was changed to depend on pymaemo-optify, so it is guaranteed to be installed along with python applications. > (We should also think about folding pymaemo-optify into maemo-optify > completely, but that can be done later as well.) Given that pymaemo-optify currently does not manipulate the packages themselves, but works at "low level" by bind-mounting Python directories, I think the _current_ version cannot be merged with maemo-optify. >> This together with the direct dependency check (i.e. looking by >> pymaemo-optify or python or python2.5 on Depends) would make a good >> heuristic (in my opinion). > > Well, the direct dependency check wouldn't do anything useful anymore, > or would it? (I.e., has-dependency || pymaemo-optify-is-installed == > pymaemo-optify-is-installed.) Yes, having pymaemo-optify installed after .deb's have been created would be a indication of that package depending (directly or indirectly) on some Python package during build. But it does not guarantee the package which maemo-deb-optify is running on actually depends on python during runtime. But I agree having just one heuristic would be better (IMHO), others could be added if/where necessary. My two cents, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
