On Fri 2010-04-30 at 08:00h, infinity2heaven wrote on ivy-user: : > Is what I'm asking that hard?
I would maybe put it this way: Ivy is a tool for library providers to make things simpler for their library users. But for the library providers themselves, doing this in a good way is not necessarily very simple, depending on the complexity of the library. The problem you have is that the providers of the libraries you're interested in either don't use Ivy at all, so you have to do their work, or they use Ivy in different ways (different conf setup etc.), so you have to do some integration work to match it up with the conventions used by other libraries, and with your own. The flexibility that makes Ivy powerful means at the same time that there are no fixed predetermined conventions, so everyone uses slightly different (or sometime very different) setups. And then Ivy only does the dependency management part, so the task of writing build scripts that meet your needs remains yours. But to answer your question: Yes, it's that hard, unfortunately. -- Niklas Matthies
