Le Sunday 01 June 2008 17:47:02 Yair K., vous avez écrit : > IIRC, there still a very few drivers which aren't open-sourced because > permissions couldn't be obtained (lynx ONE?), but everything most systems > need is available under GPLv2 only (there are CDDL/BSD versions for > OpenSolaris/FreeBSD).
Ok. What's important is that the tarball that we use doesn't contain non free code. > > * Which version should be packaged ? For instance, I have has issues with > > the libsalsa build, but as I read, it was fixed in the current > > developement version. Hence if the developpement version is stable > > enough, it could be considered for the package. > > If a developement version isn't used, than this suggest the need for a > build 1016, as build 1015: A. Won't build on Linux 2.6.26 (Debian will move > to it eventually). B. Won't build when newer ALSA is installed because of > the libsalsa issue mention above. C. Gives spurious init warnings on > 2.6.25. Fine, the two later were the issues I noticed yesterday. > > Then, a secondary packaging issue, I will change so things that the > > current system is doing. In particular, deleting the alsa modules is not > > acceptable. In debian, there is a /usr/sbin/alsa command that can be used > > to unload alsa modules, so it would better use this. > > Since ALSA can't be deleted, we'll have to blacklist ALSA modules to > prevent it from loading at boot. In Debian this can be done by > reconfiguring linux-sound-base to "OSS". Is there a way to automate this? > Or must the user do this manually? (This is important for uninstall case as > well). Well, I have to look at this. Romain _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
