On Mon, Mar 05, 2007 at 08:50:18AM -0800, [EMAIL PROTECTED] wrote: > Quoting Arnaud Vandyck <[EMAIL PROTECTED]>: > > >On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote: > >[...] > >>>I understand your point of view and respect it. But as we are > >>>responsible in some way of the software we package and distribute, we > >>>cannot distribute a software for Debian that could install non free > >>>software in all ~'s. > >> > >>Binary blobs are not non-free per so. If we would go your route we would > >>have to disable download functionality in e.g. iceweasel as you are > >>*able* to download non-free stuff with it. The download feature in Maven > >>is no problem per se. We just need to figure out how we exactly handle > >>non-installed dependencies. > > > >How was it build? What are the build/runtime dependencies? These sort > >of things will be a headache. Example: Hibernate have a dependency > >with transaction api you have to download to Sun website; Spring, > >Maven have dependencies against javamail, activation you have to > >download from Sun's website. And for the last two one, we have free > >implementations. Are these implementations in the maven repository so > >the user could use the free implementation or is (s)he obliged to use > >the Maven proprietary one? > > > >Tom Marble told me he'll work on that issue where a lot of Sun's > >libraries must be downloaded from Sun website with a click on the > >agreement, no source to build them and a non-free license (Sun > >binary...), but in the mean time, what do we do? > > There is a additional repositories that host that sort of stuff and a > lot of other libraries. E.g. the java.net maven repo has a lot of the > stuff you are talking about, the codehaus repo has a lot of other > extensions. The packaging team should not worry about that. The maven > user will with the pom for his own project. > > It is also common for maven users to create their own repository with > their build artifact and other libraries that simply are not available > anywhere in a repositoryt. it is quite simple to add one (as long as > you dont worry about its dependencies...) > > Anyway.. from a user perspective I think it would be great if it just > behaves like upstream and pumps stuff in ~/.m2 like normal.
Thats fine for some things but not for others. E.g. We can't and we are not allowed to download stuff during build time of a package. Cheers, Michael -- .''`. | Michael Koch <[EMAIL PROTECTED]> : :' : | Free Java Developer <http://www.classpath.org> `. `' | `- | 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
