maemo.org Bugzilla – Full Text Bug Listing
|maemo-launcher build-depends on libhildondesktop-dev, which in turn build-depends on maemo-launcher-dev
|[Maemo Official Platform] System software
|Carsten Munk <carsten.munk>
|Guillem Jover <guillem>
|andrey.kochanov, andre_klapper, carsten.munk, eero.tamminen, quim.gil
SOFTWARE VERSION: Using trunk versions from https://stage.maemo.org/svn/maemo/projects/haf/trunk/ We are a small bunch of people from community trying to "reconstruct" Maemo (see proposal at http://wiki.maemo.org/Maemo_Reconstructed, ), and we are attempting a sort of proof of concept of this proposal. In this PoC we take most published parts of Maemo and try to refit them onto a up-to-date Debian/Ubuntu base to see what problems arise - also to help fix problems with porting Debian/Ubuntu applications to the Maemo platform. As part of this work, we're reporting this bug to help improve Maemo and the portability of the Maemo platform. STEPS TO REPRODUCE THE PROBLEM: dpkg-buildpackage'ing hildon-desktop dpkg-buildpackage'ing maemo-launcher EXPECTED OUTCOME: Being able to compile each of these packages from bootstrap ACTUAL OUTCOME: maemo-launcher build-depends on libhildondesktop-dev, which in turn build-depends on maemo-launcher-dev. REPRODUCIBILITY: Always. EXTRA SOFTWARE INSTALLED: Not applicable. OTHER COMMENTS: WORKAROUND: in hildon-desktop: DEB_BUILD_OPTIONS=nolauncher dpkg-buildpackage dpkg -i built packages in maemo-launcher: dpkg-buildpackage and then in hildon-desktop again: dpkg-buildpackage. User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
.. and obviously a step in workaround where maemo-launcher-dev is dpkg -i'ed.
CCing also Andrey as he is supervising the Fremantle architecture.
Its the maemo-launcher Hildon booster (/usr/lib/maemo-launcher/booster-gtk.so) that requires dependency to libhildondesktop-dev. If it would be put to a separate source package, build deps should work fine like this: - libhildondesktop-dev -> maemo-launcher-dev - maemo-launcher-hildon-booster -> libhildondesktop-dev, maemo-launcher-dev
I'm a bit lost here. As this seems to be in the Desktop area and a non-critical issue (hence by default a WONTFIX for Desktop as far as I understand), I'd really like to know whether this still applies for Fremantle and whether it's worth to file an internal ticket about this. Comments appreciated (Andrey maybe?).
Just a note, cyclic Build-Depends are common in Debian, and that's one of the first issue one stomps on when bootstrapping a new port for example, but then they usually are not visible anymore. Of course those are desirable to be fixed if feasible, but sometimes it's not. Consider pkg-config using glib and glib needing pkg-config at build time, in that case pkg-config ships an old snapshot of glib so that one can bootstrap it first. (In reply to comment #3) > Its the maemo-launcher Hildon booster (/usr/lib/maemo-launcher/booster-gtk.so) > that requires dependency to libhildondesktop-dev. If it would be put to a > separate source package, build deps should work fine like this: > - libhildondesktop-dev -> maemo-launcher-dev > - maemo-launcher-hildon-booster -> libhildondesktop-dev, maemo-launcher-dev Yeah that'd be a possibility given the modular design of the launcher. Another one would be to split the hildon-desktop from the library, and as I remember there was already talk about that, maybe there's even an internal bug report.
(In reply to comment #4) > I'm a bit lost here. > As this seems to be in the Desktop area and a non-critical issue (hence by > default a WONTFIX for Desktop as far as I understand), I'd really like to know > whether this still applies for Fremantle and whether it's worth to file an > internal ticket about this. It is true that it is a non-critical and trivial issue, but I don't agree that because of this that it should be a WONTFIX. It is an issue that will improve Hildon (and launcher) adaptation outside of Maemo, and may help in case of developers internally/externally bootstrapping Maemo from scratch or in case of people using launcher in other distributions. But in reply to #5 (thanks for the informative comment), yes, it's reasonable to have some kind of circular dependancy in some cases - and even if this bug would be a WONTFIX, it is now documented so future bootstrappers will be aware this issue exists and can work with it.
Hmm, I assume this is worth importing to fix this for Fremantle?
Silence = compliance. (In reply to comment #6) > I don't agree that because of this that it should be a WONTFIX. Sorry, I've been misleading - I meant "WONTFIX for Diablo", but definitely NOT for Fremantle.
Definately WONTFIX for Diablo. My interest is in stage.maemo.org/svn/maemo/projects/haf/trunk/maemo-launcher personally, - a fix at some point would be most welcome, but not critical for SDK or actual release.
Seems to be fixed in Fremantle Beta, as libhildondesktop is seperated out from hildon-desktop. Still a pain for us as we use the old HD. Does anyone happen to know if beta libhildondesktop is still usable for the old HD?
Internal comment: "Circular dependency only seems to exist for old hildon desktop (libhildondesktop0)"
(In reply to comment #10) > Seems to be fixed in Fremantle Beta, as libhildondesktop is seperated out from > hildon-desktop. So can this be closed as FIXED?