-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Stephen,
sorry for the long delay, university is keeping me quite busy. > That'll teach me not to test stuff properly... This makes moving to > osspd a bit more difficult than it should be, since a conflicting > package will be removed but not purged: users with oss-compat > installed will still have the oss-compat.conf file around when the > install osspd, even though oss-compat is gone. > > Perhaps if I add a "deconfigure" handler to oss-compat the upgrades > will work. Ouch, that's nasty. But I don't know these module load mechanisms well enough to tell whether there's another way. > Ah OK, I've been using the Alsa backend with pretty good results > for now, I was hoping it would be good enough ;-). Incidentally I > wondered about getting osspd to auto-configure itself for Alsa or > PulseAudio depending on what the user uses, but that seems rather > hard to do properly. Interesting, I never got it to spit out any useful sound. But thanks for the report, I already thought about dropping it since I'm unable to fix bugs in it, and upstream does not consider it fully supported (at least, that's what I think... in some comment, it says that the ALSA backend is very incomplete and was mainly written to demonstrate how bad the ALSA userspace API is). What I thought about is splitting the package, to have separate packages for the backends. Then I could use update-alternatives or some other means to choose the backend. The PA backend package would be the default (and depend on PA, rather than just recommending it), but you could uninstall it and install the ALSA one instead to avoid PA. osspd would automatically switch. However, I am not sure whether that's worth the effort. > Regarding Ubuntu I'd need to check how Recommends are handled on > upgrades; aptitude and apt-get don't install them by default on > upgrades unless I'm mistaken, just when installing initially. But > Ubuntu has an upgrade tool so things might be different... And even > for Debian I don't know whether the jessie kernel will still > provide OSS modules! Ah, right... aptitude installs recommends on upgrade, I think, but I'm not sure if apt-get also does so. At least, the osspd install count is currently sky-rocketing, and I doubt that's just new installations ;-) About OSS support in the kernel, I don't know. I just don't want to step on anyone's toes, like people compiling their own kernel with OSS enabled. Personally, I consider that unsupported, but Debian is very conservative in such things, so I don't know the official stanza. In the end, you as maintainer of oss-compat can probably decide that out-of-tree kernels are not supported - and wait for complaints ;-) Kind regards Ralf -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJR1v9DAAoJEEAdTZ0mjB1WRvAIAKG9ncQ8/nNgtm6Kq8aAgt45 DAG+teyOqdrvPgoaqT/7aD37fBchnVBXwsLr38QaFp+Mxp89EAGJVXMFqdO+pacz ahxsJIRb11l83vhVB0lGcANZS7kjBCdImBZHGNmxIzzbz/8WDpnp3istEL/MPLW2 x/BhDPpxjWmgtwR7ywBmdEr3iyqNpXd3ips4YAwnzDxE1SCUvGMfWCTqDLMHT2P6 GrRIBpbzLb5VBN0yiTj/oTHnsHMWfuJcvEKSefHUopUVGjXrapIWuJx2YByjWAWG IffspUF0imZxX3LWGw8jrdZVpieG1CmTciC6o8x7dHZe9KAG4L/rjWdtXuDqh/w= =q+P8 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
