Old 19th September 2010, 16:06   #1
rahulthewall
Junior Member
 
Join Date: Apr 2010
Posts: 23
Packaging and releasing a plugin

Hello everyone,

As some of you might know we have been working on a smart shuffle plugin for Winamp, which we now believe is ready for an beta release. There are some features which we would like to add, but the plugin as of now is quite usable.

I now have some questions related to packaging the plugin. The libraries that we have used (apart from the Winamp SDK) for this project include:

- ANN (http://www.cs.umd.edu/~mount/ANN/), licensed under GNU Lesser Public License (LGPL)
- Pthread (http://sourceware.org/pthreads-win32/), also licensed under LGPL
- libcurl - licensed under a derivative of MIT/X (http://curl.haxx.se/docs/copyright.html)

What we would now like to do is to host the code of our plugin under google code, so that it is accessible to everyone. This would help us implement an issue tracking system, and collect bug reports and feature requests.

However, the question is, under what license do we now distribute our source code? Why I ask this is because we would like to distribute the needed include files from libcurl, pthread, ANN and SDK as part of the plugin source code (we would of course not claim ownership to that code).

Also, for releasing the plugin, I believe we can simply create an installer using NSIS and then upload the plugin.

Please correct me wherever I might be wrong, and do point out the right way of going about things here.

Thanks
Rahul (rahulthewall) and Chahine (Chahine).
rahulthewall is offline   Reply With Quote
Old 19th September 2010, 16:54   #2
DrO
 
Join Date: Sep 2003
Posts: 27,873
you'd just need to ensure that the license on your plug-in covers what is needed by the rest of the libraries used (which if t wasn't for libcurl you could just doe as LGPL) - i'm not sure how the MIT/X license corresponds to that though if you're referencing all of the required aspects of the licenses and libraries then there shouldn't be an issue (if you weren't being obvious about what's being used then might be issues.

for the installer, NSIS is what is recommended though there's nothing stopping you from using other installers of of your choice.

-daz
DrO is offline   Reply With Quote
Old 20th September 2010, 07:06   #3
rahulthewall
Junior Member
 
Join Date: Apr 2010
Posts: 23
Will packaging the plugin as MIT work? (Apologies, but I haven't dealt with licenses before).
rahulthewall is offline   Reply With Quote
Old 20th September 2010, 09:11   #4
DrO
 
Join Date: Sep 2003
Posts: 27,873
if you haven't already then http://www.gnu.org/licenses/lgpl.html seems to contain some info on what to do with combined licenses as http://en.wikipedia.org/wiki/MIT_License just seems to require a license reference and is GPL (so should be LGPL) compatible.

as for the question, without really working through those references i'm not 100% (i've never had to mix licenses directly myself before) and the best option is to look at other projects which have done it and see how they've done things.

-daz
DrO is offline   Reply With Quote
Reply
Go Back   Winamp & Shoutcast Forums > Developer Center > Winamp Development

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump