Hi Marcus,
On Mon, Jan 19, 2009 at 9:19 PM, Marcus Better <[email protected]> wrote: > "In a later upstream version 'c' adds another depends 'i' and that means > that we have to change all reverse depends of 'c' including 'a' (like > adding i.jar to DEB_JARS in debian/rules)." > > Only if 'i' is really a build-dep of 'a', in which case we will have to > update the build-deps of 'a' anyway, no because it is 'c' that will get a new Depends: i and all reverse (Build-)Depends of 'c' (including 'a') will profit from that - there is no need to update 'a'. In a future version of maven-debian-helper I might implement something similar to '${shlibs:Depends}' (maybe ${maven:Depends}?) and all direct (non transitive) Debian dependencies will be calculated automatically. > This is way too invasive and Maven-centric. The build system should not > dictate where files are installed in Debian. I would prefer the other way > around: symlinks in $REPO, and files installed elsewhere (for example the > current locations, to avoid moving existing files around). Okay I will change the spec to optionally allow installation of symlinks into $REPO. Cheers, Torsten _______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
