On Fri, Jun 14, 2013, at 03:47 PM, Adrian Knoth wrote: > Frankly, I don't like your idea of splitting the package and defining a > conflict between them. There has to be a better solution which allows > for co-installation. > > One could further split the jackd2 package into something like > > - jackd2-backends (all the .so files) > - jackd2-jackd (depends on jackd2-backends) > - jackd2-jackdbus (depends on jackd2-backends) > > > and allow both jackd2-jackd{,dbus} packages to be co-installable. Of > course, people can still mess it up, but at least there's a clear > separation for those who want "easy" and "I can have both" for those who > need it. >
Perhaps we could add a install script asking the user whether or not to remove the other one, and explain why they might want to do that. > > And while we're at it, let's move the manpages and the debconf files to > jackd-defaults to avoid code duplication between jackd1 and jackd2. > > _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers