[maemo-developers] Proposal: Karma-Whores protection mailing list
From: Marius Vollmer marius.vollmer at nokia.comDate: Mon Jan 4 17:16:46 EET 2010
- Previous message: Proposal: Karma-Whores protection mailing list
- Next message: Proposal: Karma-Whores protection mailing list
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ext Anderson Lizardo <anderson.lizardo at openbossa.org> 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... (We should also think about folding pymaemo-optify into maemo-optify completely, but that can be done later as well.) > If so, checking whether "pymaemo-optify" is installed on the > scratchbox target would be one heuristic to detect indirect > dependencies, Yeah, I was thinking of that, too... Maybe it is indeed good enough. > 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.)
- Previous message: Proposal: Karma-Whores protection mailing list
- Next message: Proposal: Karma-Whores protection mailing list
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]