On Fri, Apr 17, 2009 at 8:25 PM, Stephane Doyon <sdo...@chromium.org> wrote: > On Fri, 17 Apr 2009, Dean McNamee wrote: > >> Not to make more things complicated, but shouldn't it be possible to >> only use gconf if it's available, otherwise don't get the proxy >> settings? >> >> I am just worried that we are slowing sucking in the whole world into >> our dependency list. >> >> I guess we obviously need the headers for building, but at runtime it >> would be nice to just fallback instead of requiring a dependency. >> Dunno... > > AFAICT the whole GNOME world depends on gconf so that in practice > libgconf2-4 is always installed, so as a run-time dependency it shouldn't be > a problem.
Ok, makes sense. I sort of misread that this was just an announcement about installing the dev package (headers, etc). Thanks > > (It's vaguely amusing to see what apt-get wants to throw away if you ask it > to uninstall the run-time lib libgconf2-4.) > >> On Fri, Apr 17, 2009 at 5:29 PM, Stephane Doyon <sdo...@chromium.org> >> wrote: >>> >>> If you don't build on Linux, then you can stop reading now. >>> >>> I will be checking in this CL >>> (http://codereview.chromium.org/60009) >>> that will require gconf as a build dependency for Linux. >>> >>> You need to do: >>> sudo apt-get install libgconf2-dev >>> (or equivalent for your distro) >>> and if you are on a 64bits system: >>> sudo ln -s libgconf-2.so.4 /usr/lib32/libgconf-2.so >>> >>> maruel@ has been kind enough to update the build slaves. >>> I have also updated the wiki, and the build/install-build-deps.sh script >>> will be updated by the same CL. >>> >>> I'll wait until Monday so people have a chance to see this. >>> >>> Thanks >>> >>> >>> >>> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
