On Monday 02 June 2008 00:12:27 Romain Beauxis wrote:
> Hi all !
Hi,
A few notes:
[snip]
> * Is it the whole code GPLed ? (naive question)
> I mean that even if the global licence is GPL, there could be other parts
> which are not GPL. This could also include the documentation that could be
> GFDL for instance.. Those licencing questions are very important for an
> inclusion, and often thake time to check (and are really boring too), so your
> help is welcome here :)
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).
> * 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.
[snip]
> 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).
Yours,
Yair K.
_______________________________________________
oss-devel mailing list
oss-devel@mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel
