On Wed, 2005-12-14 at 19:39 +0100, Karl Trygve Kalleberg wrote:
> Joshua Nichols wrote:
< SNIPPED >
> > This leads to the question of where, then, to get the jars from. I had
> > first thought at build time, we could populate a local repository with
> > symlinks to jars that we provide from packages. This would work, and
> > could be automated to some extent, but I think it would be tedious to
> > maintain a list of jars that each package needs.
> Even in the face of such tedium, there is one thing this gives us that
> your suggestion does not: the ability to actually check for hidden
I'm a little confused by the above statement. Are you agreeing with
Josh, or disagreeing? In other words, are you in favor of the tedium
because it gives the ability to check for hidden dependencies?
> If we create a local, minimal .jar environment for each maven-built
> package, we know exactly which jars (and therefore which ebuilds) it
> depends on.
This sounds like what Josh was suggesting in one way, but I can't be
sure if you're saying that you like his idea or rather the idea of
making smaller, separate repositories. Just wondering.
> In the case where maven itself goes into the system and looks around for
> .jars that are there, we may quickly end up with it depending on stuff
> we didn't see.
I agree, although this really is an upstream problem I think. If they
aren't even properly documenting what libraries their application
depends on, I see that as a bigger problem we shouldn't necessarily try
to fix for them. I understand that this does happen in the real world,