similar to: Vorbis licensing...

> ok, > This is something I want to ask for some time now :) > Does this mean that License issues works with wine as it > works with the Linux kernel? > The Linux kernel is GPLed, however if a module (driver) is > dynamic loadable, it can have a proprietary license. > Is this the way it works with wine? The core (wine itself) > is LGPL, however its modules (builtin

It is my understanding that R is licensed under the GPL with the exception of a few header files for the purposes of linking binary code with R under non-GPL licenses. However, the R-base package itself is licensed under the GPL, as are many (but not all) packages in CRAN. Furthermore, basically any R script will use functionality from R-base. As I understand it, the situation isn't

Hi every one, I have an unfortunate need to release a closed source BeOS media codec for Vorbis, basically I'm using headers under an NDA so I can't release them. (Yeah I know closed source boo hiss). So I have a couple of question about what I need to do for all this to be above board. I've made no changes to the libraries so thats not a problem. As far as I can see as

Are there any thoughts to changing the license used by Vorbis from the GPL to the LGPL? As it stands, linking to libvorbis will taint any program. I'd like to research using Vorbis and contribute to it, but I'm not at the liberty to GPL the engine I'd like to link with libvorbis. The GPL prevents me from using it. The LGPL would still protect the Vorbis code while allowing

Are there any thoughts to changing the license used by Vorbis from the GPL to the LGPL? As it stands, linking to libvorbis will taint any program. I'd like to research using Vorbis and contribute to it, but I'm not at the liberty to GPL the engine I'd like to link with libvorbis. The GPL prevents me from using it. The LGPL would still protect the Vorbis code while allowing

>>The game companies are interested in >>Vorbis, and this is a good thing :) I am a lead programmer at a major game company (Maxis) and Vorbis is potentially very important to us. I am pushing to make it the default streaming sound format (e.g. non-sound effects) for all future titles. This assumes that it works as well as anticipated. Other subdivisions of Electronic Arts are

Hi, I wanted to let you know that I have just made available the sources to the ogg + vorbis implementation in haXe, which I've been working on for last couple of weeks. The code compiles to an swf file playable in Flash Player 10. A demo of a simple player implementation (latest Flash 10 required): http://people.xiph.org/~arek/pg/hx/test.html and the sources, in a bzr branch, currently

Hi, I wanted to let you know that I have just made available the sources to the ogg + vorbis implementation in haXe, which I've been working on for last couple of weeks. The code compiles to an swf file playable in Flash Player 10. A demo of a simple player implementation (latest Flash 10 required): http://people.xiph.org/~arek/pg/hx/test.html and the sources, in a bzr branch, currently

Hi, We would like to announce the first release of the Speex project. Speex (http://speex.sourceforge.net) is an open-source (LGPL), patent-free compression format allowing an alternative to expensive proprietary codecs. Unlike Ogg Vorbis which compresses general audio, Speex is designed especially for speech. For that reason, Speex is meant to be a complement to Vorbis. Since it is specialized

I manage the audio-video section of the GNU web site http://audio-video.gnu.org/. I have tried the Theora codec and am very impressed by the level of integration with free desktops and the bit rate/quality combinations. I intend to move all video content to the Theora codec partly for technical reasons but mainly to promote free and open formats. I do have longer term worries, projecting

Possibly more of a legal question than a technical development question, but here goes. In the doc\COPYRIGHTS file it is made clear that the intention is that you can write R packages and distribute them under licenses not compatible with GPL, by making the relevant header files available under the LGPL. This was an explicit change that was made in February 2001, and allows for DLLs that

Hello, On the Windows platform, I would like to compile a version of the codec files ogg.dll, vorbis.dll, and vorbisfile.dll that are small. I notice that the provided Windows projects are very large...the release Vorbis.dll is > 1 mb. To me, that is huge. I am only using decoding features. I looked in the Zinf project, and they seem to have a version with the encoding functions

Hi, I've ditched the idea of calling the oggvorbis .dlls, and I'm compiling the 1.0beta3 source into my own dll. After opening as "rb" instead of "r", the ov_open() call works. However, ov_read() seems to consistently read less data than I ask for. My buffer is enough to hold two seconds of data, 16 bit 44k mono, that's 176400 bytes. The first call to ov_read()

Hi Kovacs, >subj. I can compile the library on vc6, but it seems that it doesn't >export anything. Has somebody similar experience? I've built it using VC6, though I didn't use the project files in the vorbis_vc6 subdirectory, so I can't comment on them. You should be building the library as a static library, and not a DLL -- if you want to build the library as a DLL,

Hoping someone can clear up a licencing question... My understanding is that R is licensed under the GPL, with some headers licensed under the LGPL (per COPYRIGHTS, so that R plugins don't have to be GPL - arguably incorrect, but besides the point). JRI states that it is licensed under the LGPL - but it links against R shared libraries (or so is my understanding - please correct me if I'm

On Fri, Nov 26, 2010 at 10:03:05AM -0800, Yandell, Henri wrote: > We?re looking into using Hivex and came across something odd. While > the license of hivex.c is LGPL 2.1, it appears to require the GPL > 3.0 licensed gnulib package for a few minor functions ( full_read, > full_write and c_toupper ). There are also a few GPL 3.0 build > files. It has always been our intention to

Dear Samba team, We have developed cross-platform multiprotocol intranet file searcher and it includes the module (SMB scanner for *nix) which uses libsmbclient to enumerate all files on smb shares ("uses" means including headers and linking with library). Other modules also use some external libraries, but all other libraries have LGPL license. We prefer to publish our

I've got a bug pending for FreeAmp right now where the vorbis metadata plugin does not handle international characters right. The comments that are returned from vorbis_comment_query() are in UTF-8, but FreeAmp is ISO 8859-1. I've been looking for a UTF-8 --> ISO 8859-1 converter that is available for inclusion in a GPL/LGPL program and is reasonably small. There are many full blown

Afternoon all. I was discussing the current licensing of Xapian and how it influences the way we work with someone at another OSS project recently, and although the upshot is likely to be that they'll amend their license (it's a corporate foundation, and GPL compatibility is something they desire for precisely this reason), it did prompt me to think about how we're tracking where we

Note I'm not asking for any legal advice here obviously, simply what the intention of the R foundation is with regard to allowing commercial connection to R. I've looked at various threads on the r-devel archive and it looks like this may have been discussed before, but as far as could tell, not to any great resolution, and not, it seems, specifically covering this angle. In the