Re: Mapping dependencies between Gnome modules

[Daniel Dewey <ddewey sei cmu edu>]

> Hi,
>
> Thanks for the dpkg tip, but I have found that Debian packages and Gnome 
> modules don't tend to correspond particularly closely to one another 
> (there is often no Debian package for a Gnome module). That software 
> sounds great for Debian dependencies though.
>
> I was able to find the XML files JHBuild uses for Gnome's dependencies 
> and that takes care of my needs for now:
> http://svn.gnome.org/svn/jhbuild/trunk/modulesets/
>
> ~Daniel
>
> ps- I also got an error (pdf was corrupted) on 
> http://turingmachine.org/~dmg/temp/wcre.pdf
> _______________________________________________
> academia-list mailing list
> academia-list gnome org
> http://mail.gnome.org/mailman/listinfo/academia-list
>   

Well, it turns out that jhbuild seems to be missing a lot of dependency 
information (for example, devilspie is a gnome module 
<http://svn.gnome.org/svn/devilspie/> that jhbuild is unaware of). I 
could, as some people have suggested, move to mapping the dependencies 
between packages in some distro like Debian (using dpkg) or the 
compromised, but pretty good, dependencies in jhbuild; I could try to 
sort through the source code of all of GNOME's packages to find the 
dependencies; I could start a non-code-based analysis such as the 
"logical coupling based on release history"; or... something else?
Any suggestions?
Thanks,
~Daniel