Le Monday 02 June 2008 04:04:51 Hannu Savolainen, vous avez écrit : > > First of all, concerning the licence: > > * 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 :) > > > > There are some closed source packages in OSS but they are not included > in the tarballs. So all drivers included in the GPL source package are > under GPL. Some header files and/or sample programs may be under the BSD > license but all this code is for user land only.
Well, that's what I was afraid of.. The debian/copyright file has to report each file's licence if it differs from main licence. I means I'll have to go through each of them to check the licence.. > > * 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. > > > > The development version (in particular the hg one) is too dangerous to > be used in "production". The 4.0 version is safe but may lack some bug > fixes (we have been trying to include most of them in v4.0 too). > > We have planned to make v4.1 the "stable" version after the summer. So > it might be a good idea to wait few months before inclusion. Sure I can wait ! > > Then module-assistant would unpack the tarball > > in /usr/src/modules/oss4-modules, build them there and create a debian > > package from the resulting modules. That way, the user obtain also a .deb > > for the modules, which can be removed, upgraded etc.. > > > > Would it be possible ? > > > > The main problem when installing OSS4 in Linux is that that the kernel > development environment (kernel-headers, gcc, binutils, etc) needs to be > installed in the target system. This is something I would like to get > fixed. So (IMHO) including anything that needs to be compiled in the > .deb files is not good idea. Well, compiling on the user's system is the standard way to distribute external kernel modules in debian. In particular, module-assistant does exactly the job of installing the kernel devel. environment. Romain _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
