4 ms·
Have been using this repo for a long time now, and now deploys are broken :( going to have to re-write some code i guess...
by kernelcurry 11y ago
Have been using this repo for a long time now, and now deploys are broken :( going to have to re-write some code i guess...
- orclev 11y agoShould probably use https://github.com/tecnickcom/tc-lib-barcode https://github.com/tecnickcom/tc-lib-barcode or https://github.com/tecnickcom/TCPDF https://github.com/tecnickcom/TCPDF both of which are mentioned in the DMCA notice.
- wiredfool 11y agoAnd do a license review to see if the gplv3 license imposes any cconditions on the use of the code.
- ealexhudson 11y agoGPLv3 doesn't impose any conditions on use. This is LGPLv3, which has even fewer requirements.
- orclev 11y agoActually it does which is kind of the point, it's just those conditions are fairly easy to meet. The TL;DR: version is that if you use LGPL code in your project you have to redistribute the source code of that LGPL code including copyright notices. In practice that requirement can usually be fulfilled by simply providing a link someplace convenient to wherever you original got the code from yourself so it's pretty easy to comply with. Additionally GPL and LGPL differ primarily in that GPL requires that code that uses it must itself be licensed under GPL, where as LGPL allows non-LGPL code to be linked to LGPL code (so long as the conditions of the LGPL code are still being met, primarily the distribution clause). The big difference between GPLv2 and GPLv3 was mostly about closing some loopholes that some companies (primarily TiVo) used to make it impossible to modify certain GPL code on their devices (mainly this involved using hardware DRM). This obviously violated the spirit of the GPL because the whole point is to allow for people to tinker with the code, and preventing that by coupling it to proprietary hardware as a end run around the GPL necessitated the creation of GPLv3 specifically to make doing that a violation of the license.
- wiredfool 11y agoNever mind, didn't see that it was LGPL.
- wiredfool 11y agoAnd I was thinking of the AGPL3, which would affect usage.
- dragonwriter 11y ago> GPLv3 doesn't impose any conditions on use. This is not true, GPLv3 has use conditions which are conditioned on the target market of the product. > This is LGPLv3, which has even fewer requirements. OTOH, this is true.
- kernelcurry 11y agohttps://tldrlegal.com/license/gnu-lesser-general-public-license-v3-(lgpl-3) https://tldrlegal.com/license/gnu-lesser-general-public-lice...
- ealexhudson 11y agoGPLv3 doesn't have any use conditions; it's free to use, for any purpose. You are probably thinking of the conditions on the things that aren't use - modification, distribution, etc.
- 525 11y agoOr not deploy from random repos you don't control.
- Sanddancer 11y agoIf you've been using the repo for a long time and you didn't have a local copy to use in case github went down, etc, your deploy was already broken. Having local mirrors of third party repos, and pulling those into your build system is fairly trivial, and will save a lot of heartache in cases like this.
- noir_lord 11y agoEspecially if you want to be sure that a version you pegged exactly for stability will be around in a year or two (looking at you node land).
- cbd1984 11y agoIf I knew someone was deploying from one of my repos, changing my code to make their site ALL PONIES ALL THE TIME U GUISE would honestly occur to me. It would occur to me, and I might not be strong enough to resist. PONIES!