<div class="gmail_quote">On Thu, Aug 26, 2010 at 3:54 AM, Paul Bender <<a href="mailto:pebender@san.rr.com">pebender@san.rr.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> On 8/24/2010 5:48 PM, Enrico Weigelt wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> * Dan Nicholson<<a href="mailto:dbn.lists@gmail.com" target="_blank">dbn.lists@gmail.com</a>> schrieb: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> It might be easier to avoid the inevitable complaints and keep the bundled library. Otherwise we're basically shifting the support burdento the glib folks. </blockquote> And to hundreds of individual package maintainers. Circular dependencies are an NO GO in clean software engineering ;-O </blockquote> I agree that circular dependencies are very annoying when building a system from scratch (as I do with MiniMyth). However, I agree that continuing to have a a dependency (whether internal or external) on a package that is essentially obsolete is very annoying. Maybe a solution is to adopt the solution that GCC adopts for its circular dependency on packages such as gmp, mpc and mpfr. If you have extracted these packages to the top level directory of gcc, then it will compile and use those. Otherwise, it will attempt to use the versions of these libraries installed on the system. </blockquote><div> another solution: remove glib dep :p You need some string functions (easy to do), single linked list (easy to do) and hash table (a bit less easy to do). Vincent Torri </div></div>