Homebrew Ok, about GPL stuff. Please explain

  • Thread starter Thread starter DeadlyFoez
  • Start date Start date
  • Views Views 8,157
  • Replies Replies 65
yellow:

I wasn't claiming he couldn't use wii.py, I said that our license still carries over. so any binary he shares that has our license must have source available. the modified code is the issue since he can't just link to svn.
 
so is giving credit to u guys enough? Or do I need to include a specific *.txt file with the NUSAD download?

edit:

@megazig,
Leathl is really busy IRL right now, but before I decided to close down NUSAD I requested he either update the svn or send me the source.
 
Why don't you just upload all the code in a zip file and link to it. Is it that hard?

I decided to make Wii.py GPL licensed so that the community can benefit from all things that are using it. Not providing the source is against what Wii.py (and thus libwiisharp, as well, since it is a translation) is for.
 
If its all the same, when/if I re-open NUSAD, I'd prefer linking to each source individually (it would make it a lot easier once dependencies start getting replaced/removed). Not to mention that it would mean that if some1 wants the complete source, they would be forced to view each supporting apps' homepage, which is great for the original devs.
 
Okay, if some1 can spell out exactly what I need to do to make NUSAD GPL compliant, there will be a much greater chance I will eventually re-open NUSAD. I've thanked everyone I have to (I think), and I've provided links to the sources of the underlying apps/files (these sources are for the EXACT binaries included in NUSAD, I got some of this info from Leathl and cwstjdenobs just today, thx for getting back to me so quickly guys!), and I state that the NUSAD source code is available upon request

Below is an example of what I would include in the NUSAD thread in order to make it GPL compliant. Can someone please let me know if this satisfies GPL requirements? And if not, what else specifically would I need to do to make it GPl complaint?
********************************************************************************


NUSAD SOURCE CODE AVAILABLE UPON REQUEST (not sure if I have to make it available at all, but I have no problem making it available upon request anyways)

Credits:
Special thanks to the following people, who have gone out of their way numerous times to help me when they didn't have to
  • Leathl, cwstjdenobs, DeadlyFoez, Da Mystery Man, Giantpune, WiiCrazy, WiiPower, Pepxl, longtom1, tj_cool, Violator, and xzxero.
  • Thanks to my cuz, Violator, who first got me into the Wii scene.
  • tj_cool and xzxero for their Guides (and for inviting me to join 'the Crew')
  • Team Twiizers for creating the revolutionary HackMii Installer.
  • Waninkoko for creating CIOS and other excellent apps like WAD manager.
  • Hermes for creating his efficient CIOS 222/223/224.
  • Comex for creating the heavily utilized bannerbomb exploit.
  • Crediar, phpgeek and daco taco for brick protection via Priiloader.
  • cwstjdenobs for creating the YAWMM, my personal favourite WAD Manager.
  • Arikado and the Dop-Mii team for Dop-Mii and the Fakesign Restorer.
  • WiiWu and the Dop-Mii team for MMM.
  • Leathl for libwiisharp, patchios, nusfilegrabber, showmiiwads etc.
  • WB3000 for creating the first incredible NUS Downloader.
  • WiiNinja for creating the command line version of nusd.
  • WiiPower for Neogamma and much more.
  • WiiCrazy for Crap (Forwarder Channel Maker) and Crazy Intro.
  • Wiigator for creating his Gamecube Backup Launcher.
  • oggzee, usptactical, gannon and Dr.Clipper for Configurable USB Loader.
  • Giantpune for USB Loader GX and much more.
  • Fig2k4 for Wii Backup manager.
  • DeadlyFoez for his brick fixing tutorials (and for just being Deadly).
  • Pepxl for his awesome graphics work (including the icon for this app).
  • Wii.py devs: Megazig, Omega, Xuzz, SquidMan, Matt_P and The Lemon Man
  • Daeken for writing Struct.py and marcan for his LZ77 code
  • All my beta testers!
Supporting Programs/Files Embedded in 'NUS Auto Downloader.exe':
 
Ummm, what am I supposed to do with that? Am I supposed to add something like:

libWiiSharp.dll (by Leathl) (LINK TO SOURCE) --> based on Wii.Py (LINK TO SOURCE)

then I would have to do the same thing for nusd.exe and the source code it is based on (WB3000's Gui NUSD code)

I think that's overkill... but if that is what it is going to take to make u happy then that can be arranged (even if it is above and beyond what is required by GPL)

edit: maybe it wasn't clear, but I'm expecting an answer
biggrin.gif
 
XFlak said:
Okay, i'm trying to catch up, so bear with me... I may edit this post a few times, lol

-the DIFF files are included in the SUPPORT Folder, u can't miss it
-is it alright to provide one txt file with the app that has links to where all the different sources can be downloaded. Or do I need to actually gather all the sources and upload them into one package where people can download it?
-since this is just a batch file converted to exe, all it is is a bunch commands to other apps... am I to understand that since this is 'nothing special' (for lack of a better term) that I don't need to provide the source of the batch file, but only the source of the supporting apps/files?


edit: and what about crediting sources? For example, LibWiiSharp is based on Wii.py, do I need to credit the developers of LibWiiSharp, or Wii.py, or both? What if Wii.py was based on someone else's work? Would I need to credit them too? How far back do I need to go when crediting people? FYI, I have no problem giving credit where credit is due, I just want to know the minimum I am required to credit as my credit list is already massive (also note that I even credit a lot of people that I don't have to)

K found the .diff files. Sorry about that...

As far as source goes, it is NOT enough to provide links. You must provide the source yourself. This can include a separate source package if you want, but YOU have to do it. The main reason for this is the question of what if the link you point to ceases to be valid, or if you point to a source control repo, there are several versions available, so you need to package everything source-wise that would be necessary to rebuild every GPL binary you release. Also, it's supposed to be released in the same manner as the binaries, so typically that means either all in the same .zip or else if you do release source separately it should be uploaded to the same webhost as the binaries. Basically, if I can't build it from scratch and have it work the same as the binary you provided, you haven't included everything. Also, there really should be much clearer documentation of what applications were used and crediting their respective authors.

I've had my own experience with running afoul of the GPL. It's a pain to dig out of, but once you understand it better it gets a lot easier.
 
You could always call it done, ignore them, and make them take your ass to judge judy if they really care that much. (hint: they don't)
 
@qwertymodo,

I could easily put together a package of all the different sources (except FSUM, I don't think the source is fully available
frown.gif
)... but what about apps that are not part of GPL? Like FSUM for example (also jptch, 7za and wget)? Aren't those treated differently?
 
XFlak said:
So providing the source upon request is acceptable?

What about crediting sources? For example, LibWiiSharp is based on Wii.py, do I need to credit the developers of LibWiiSharp, or Wii.py, or both? What if Wii.py was based on someone else's work? Would I need to credit them too? How far back do I need to go when crediting people? FYI, I have no problem giving credit where credit is due, I just want to know the minimum I am required to credit as my credit list is already massive (also note that I even credit a lot of people that I don't have to)

Providing the source upon request is *technically* acceptable. However, it is much more common to release the source in the same way the binaries are released (i.e. sites like SourceForge or GoogleCode provide source and binary downloads. If you're using MF, MU, RS, etc. it would be best to package and upload your source there as well). The main thing is, if you do want to go the "upon request" route, it has to come FROM YOU. You can't just send them to the project author's site to download it there. It really is much easier to just package, release, and link.

As far as "credit" goes, that's a more gray area legally. You do need to maintain all copyright notices, but mostly that's all contained in the source code anyway so you're taken care of there. As far as the "Credit to:" list you're compiling, that's more just a matter of good manners and respect for authors who have put large amounts of work into these projects which you are now able to pick up for free and use for your own purposes. It's only polite to credit them (and proper credits will go a long way towards avoiding ugliness like you've experienced here). As long as the copyright notices are properly maintained in the source release, you are not *required* to explicitly give credit in your documentation or posting. However, like I said, it's still a good idea and the right thing to do.
 
XFlak said:
@qwertymodo,

I could easily put together a package of all the different sources (except FSUM, I don't think the source is fully available
frown.gif
)... but what about apps that are not part of GPL? Like FSUM for example (also jptch, 7za and wget)? Aren't those treated differently?

7-zip is LGPL, which is less restrictive than the GPL, but in your case just treat it the same as GPL. Same with wget. FSUM unfortunately appears to be commercial shareware and you probably need to remove it completely and replace it with an alternative (it's EULA probably prohibits redistribution of any modification to the application, which DOES include simply repackaging like this)

EDIT: Yeah, FSUM's gotta go. Definitely against its license to include it. What types of checksums are you using it for specifically? I may be able to help you find a suitable replacement.
 
whoops re FSUM... looks like I will need to actually modify the app itself once I find a suitable replacement.

Any chance anyone knows of a good md5 hash checker that I am allowed to repackage (under GPL, LGPL or w/e)? Preferably one that is able to perform recursive checks.

so basically if I put the source code for all the bundled apps/files into a single download package, it will be acceptable?

So I would need to include the source for libwiisharp (for example), but not the source for what it was based on (ie. wii.py), correct?

edit: wow, u offered to help me find a replacement before I even asked! Thanks man! I'm just using it to check for missing or changed files, could be *.wads, *.apps, *.dols, *.elfs, etc. I would prefer one that can check multiple folders (recursively) using a single command. If you need more of a description let me know! For my purposes even an SFV checker could probably work just as good (but I still prefer md5 if I have a choice).
 
I've having troubles figuring out how to get it to calculate md5 hash's....???? I'll keep trying, but this is not as simple as it looks, that's for sure

edit: u don't have any other recommended replacements by any chance do u? So far I'm not really feeling this one... but like I said, I'm still trying to figure it out (the help file isn't very helpful, lol). Thanks a lot!!!!
 
and we have a winner!!!

Thanks a lot qwertymodo!!!

I'll have to take a closer look at this later on after my exam, but it shouldn't be much work, and this cmd line app will definitely work just as good as FSUM!

Thank you Thank you Thank you!!!

edit: going out now for a bit, so I won't be very responsive for the next little while. Thanks again for all your help, and I'll check up on this thread when I get back in. Cheers
biggrin.gif
 

Site & Scene News

Popular threads in this forum