Re: [Amsn-devel] OT: amsn dependencies map

2009-01-18 Thread Youness Alaoui
hehe, yeah, and it doesn't really matter since it's debian and the dependencies are all automatic.. and most of the time only tcl/tk gets installed because everything else is already there... about docker, I think it's an old dependency that they never removed.. and python.. is because we have a s

Re: [Amsn-devel] OT: amsn dependencies map

2009-01-15 Thread Stéphane Bisinger
Hi, 2009/1/15 Youness Alaoui : > And to think that we always hoped for 'minimal dependencies' there are a lot > more than I thought! and we already depend on libglib! lol... I don't think there are too many direct dependencies for aMSN and actually many of these are there because of the way debia

Re: [Amsn-devel] OT: amsn dependencies map

2009-01-15 Thread Youness Alaoui
Hi, Cool, this is really nice and quite informative! And to think that we always hoped for 'minimal dependencies' there are a lot more than I thought! and we already depend on libglib! lol... I can't wait to see how it will look like with the gstreamer dependencies! :D On Wed, Jan 14, 2009 at 10

[Amsn-devel] OT: amsn dependencies map

2009-01-14 Thread Pablo Castellano
Hi! I have just found a tool to create a dependencies map of any package in Debian. You can see how "dependent" amsn is on other packages. It's not complete because Debian has not the latest version of amsn and therefore things like farsight are not present, but it's curious :) The image is here: