<div dir="ltr"><div>Ha! :) Yeah, I guess it would, though I have no idea what dogfooding run means. </div>GPL purports to be free, but it's not. If a piece of software was free, you could encorporate it into your own software that you need to be proprietary. So many times I find something I think is great and I want to use it but...oh...crap...it's GPL; can't use it. In other words, GPL is a pain for in-house development, and it's an infectious license that spreads from one GPL project to another. If I want to use GPL software, I have to use the GPL license, if my understanding is correct. <div> </div></div><div class="gmail_extra"> <div class="gmail_quote">On Thu, Dec 8, 2016 at 9:29 PM, Scott Sweeny <<a href="mailto:scott.sweeny@canonical.com" target="_blank">scott.sweeny@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That would make for an interesting dogfooding run since the tool itself is GPL-3 :-) ~S <div class="HOEnZb"><div class="h5"> On Thu, Dec 08, 2016 at 07:42:36PM -0700, Spencer wrote: > Uh...but if I use your tool, then I can't claim ignorance when I'm getting sued for copyright violations. > > Seriously, though, I hate all the legal crap licensing causes in the development world. Your tool could make life a lot easier in that regard, which is nice. > > BTW, the GPL is the worst license ever. Your lint tool should flag its use as a fatal error. > > > On Dec 8, 2016, at 2:44 PM, Scott Sweeny <<a href="mailto:scott.sweeny@canonical.com">scott.sweeny@canonical.com</a>> wrote: > > > > Hi all, > > > > I'm writing to announce a tool I've been working on to encode best > > practices for snapping software. Inspired by utilities like lintian I've > > decided to name it 'snaplint'. At this point I'd like some wider > > feedback as I try to make it more useful. > > > > Right now you can run snaplint against your snapcraft project directory > > and it will scan the prime subdirectory for the following things: > > > > * copyright (basically that you included usr/share/doc/*copyright* for > > any stage-packages > > * developer cruft (things like header and object files or static libs > > that might have made their way into your snap) > > * libraries (examine the ELF files in your snap and look for libraries > > which aren't used) > > > > The next things I'm planning on adding are: > > * checking for copyright info from apps/parts themselves. > > * checking for mixing of incompatible licenses > > > > I would love to hear suggestions from you on further improvements. > > > > You can find the source at <a href="https://github.com/ssweeny/snaplint" rel="noreferrer" target="_blank">https://github.com/ssweeny/snaplint</a> > > > > And, of course you can try it on your own machine with > > > > $ snap install snaplint > > $ snaplint <path/to/your/project> > > > > Cheers, > > ~Scott > > > > -- > > Snapcraft mailing list > > <a href="mailto:Snapcraft@lists.snapcraft.io">Snapcraft@lists.snapcraft.io</a> > > Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snapcraft</a> > > -- > Snapcraft mailing list > <a href="mailto:Snapcraft@lists.snapcraft.io">Snapcraft@lists.snapcraft.io</a> > Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snapcraft</a> > </div></div> -- Snapcraft mailing list <a href="mailto:Snapcraft@lists.snapcraft.io">Snapcraft@lists.snapcraft.io</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snapcraft</a> </blockquote></div> </div>