kicad-developers team mailing list archive

[Chris Pavlina <pavlina.chris@xxxxxxxxx>]

To be entirely honest and somewhat opinionated, I have no problem telling
Debian users that they chose a distribution that tampers with packages and so
they get to live with it. KiCad's easy to build anyway, should they decide they
don't like that choice.

Perhaps we could provide our own Debian and Ubuntu packages, like the Ubuntu
nightly PPA.

On Mon, May 02, 2016 at 03:35:48PM -0400, Wayne Stambaugh wrote:
> On 5/2/2016 3:25 PM, Nick Østergaard wrote:
> > 2016-05-02 21:09 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> >> Do we have any Debian developers on our mailing list?  I though I saw a
> >> Simon Richter on Planet Debian.  Is that you Simon?  Can someone tell me
> >> why the Debian package devs decided to build KiCad with the GitHub
> >> plugin disabled?  Is it a build issue or a licensing issue?
> > 
> > Because of OpenSSL licensing stuff...
> > 
> > Citing the debian packager:
> > 
> > "I had to remove the Github plugin from the build process, because this
> > plugins needed to compile a binary which is linked to GPLed libraries
> > and to OpenSSL at the same time, which triggers a fata Lintian error
> > about license incompatibility. However as the package kicad-common
> > provides all the know pretty libraies, and as the default template
> > declares those libraries, there is no immediate drawback.
> > 
> > Best regards, Georges."
> > 
> > -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794311
> 
> No immediate drawback for Debian when the bug reports come to us.  I
> guess we tell users no github plugin for you.  They will have to update
> their fp-lib-table accordingly.
> 
> > 
> >> Avhttp is
> >> licensed under the boost license so it shouldn't be due to licensing
> >> issues.  A warning would have been nice before we were blind sided by a
> >> bunch of bug reports.  I don't have time to look it up right now so if
> >> someone has time to do some digging I would appreciate it.
> > 
> > I think this has been mentioned on the list before. Part of the goal
> > with the curl instead of avhttp was to remove the dependency on
> > openssl, which debian rejects... Because libcurl can use gnutls in
> > debian.
> > 
> > I know it is hard to remeber everything, but people tried to warn us
> > in https://lists.launchpad.net/kicad-developers/msg22543.html
> > 
> > I got so confused with all the agressive reverts of the curl stuff
> > that I don't even know if we use that now.
> 
> We now use libcurl so if Debain's libcurl is compliant than there should
> be no issues packaging with the github plugin enabled for the
> development branch.
> 
> > 
> >>
> >> Thanks,
> >>
> >> Wayne
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp