Il giorno sab, 22/07/2006 alle 12.48 -0600, Brent Smith ha scritto: > This weekend I have tried to build Yelp and all it's dependencies from > jhbuild. I ran in to quite a few problems, so I'm complaining publicly > here (I know Jeff will hate me for this): > > * avahi depends on libgdbm; libgdbm-dev needs to be installed for avahi > Do we currently have a list of "external" development libraries that > need to be installed in order to compile from JHBuild? I know there are > some recommendations at http://live.gnome.org/JhbuildOnUbuntu in the > section "How to prepare your system for Development?" but this is 1) > not distribution agnostic and 2) relatively unmaintained. Perhaps this > could be one of the Build Brigade's responsibilities? > (http://live.gnome.org/BuildBrigade)
It's a wiki. Edit the page and add this info, please. There is this page too: http://live.gnome.org/JhbuildDependencies > * avahi depends on libglade; need to modify the gnome-2.16 moduleset to > reflect this dependency > > * avahi depends on pygtk (and pycairo, pygobject); need to modify > gnome-2.16 moduleset to reflect this dependency Could you please open a bug for jhbuild->modulets (something like "missing deps for avahi"), write that info and add myself in CC? I'll fix this. > * avahi depends on dbus-python and dbus-glib bindings set; dbus-python > and dbus-glib are now in a git repository (bug 347674); need to add to > modulesets and add appropriate dependencies I've commited the patch just now. Unfortunately no way to build a python (setup.py) module in jhbuild.. Or not? Any info? > * dbus-python depends on Pyrex for bindings which aren't included in > jhbuild bootstrap I don't think we need to put it in bootstrap, but yes, we need it. Unfortunately, as above, installation based on setup.py :-( My suggestion (and the proper solution, I think) is write this info in live.gnome.org/JhbuildIssues/* pages. Please create a new page for dbus-python and add here relevant info. (download Pyrex, unpack and run `jhbuild run python setup.py install`) > * dbus-glib fails compilation due to automake failing because of a > missing 'ChangeLog' (f.d.o bug 7540) > > * dbus-glib/test/glib/test-service-glib.h fails compilation due to a > missing include file (f.d.o. bug 7589) > > * dbus-glib doesn't install dbus-glib.h include file (f.d.o. bug 7562) All fixed. So I commited the patch in bug 347674 > * PolicyKit needs --disable-docbook-docs, or make fails due to missing > command "no" (f.d.o. bug 7161) > > * PolicyKit needs --with-pam-module-dir=prefix + '/lib' so it doesn't > try to install into /lib > Add custom rules to general moduleset is not good IMHO. When, for istance, bug 7161 will be fixed, the custom rule to general moduleset will be deprecated. As above, open a page on live.gnome.org/JhbuildIssues/ > * libvolume_id needs to be installed for hal; should this be part of > jhbuild bootstrap or should the user be responsible for installing the > development package from their distro? I ended up getting around this > by doing the following: > > cvs -d :pserver:[EMAIL PROTECTED]:/cvs/hal co -D 'Jul 10 > 18:30:00 2006 UTC' hal This is a serious issue. libvolume_id should be in udev > 0.9x (or similar). So you should install it, maybe breaking your distro. Should we depend on latest HAL package? I suggest you to open a bug about i. > Thank you, Thank your for tracking those stuff. _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
