Hi Gregor,

Gregor Riepl a écrit :
> > It is uninstallable in Jessie and even in Stretch, due to the GCC-5
> > transition.
> 
> I'm a bit confused there. How is gcc-5 affecting uninstallation?

Sorry, I rephrase: Kicad 4.0.0~rc1 is *not* installable in a Jessie
environment now, as long as you want to keep other packages qui depend on
libc prior to gcc-5.

> > I could build a backport for Jessie, and this one works too; I shall
> > launch a new build for it shortly (some packaging bugs have been fixed
> > since I tried the first backport).
> > 
> > The new release cannot be published immediately, because the new source
> > package builds new binary packages, like kicad-doc-nl, so somebody from
> > ftpmasters will have to bless the new revision.
> 
> Nice!

One ftpmaster approved the new release today. So it has become part of Sid.

> 
> > 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.
> 
> This is a bit of sad news, really, as the github plugin is very useful to
> quickly pull in external part libraries. Also makes it easy to share your
> footprints with others.
> 
> Maybe a modification to use gnutls instead is possible?
> I'll post a request to Launchpad, if that makes sense to you.

It does make sense, because of the Lintian error which is triggered.
There are three complementary ways to fix the license issue:

1 - no direct link from the GPLed code to OpenSSL libraries : when
    necessary, a command implying OpenSSL stuff is forked in another
    thread
2 - get a special authorization to link OpenSSL's library with Kicad's
    GPLed code
3 - use gnutls instead of openssl.

I fear that in either case this job is not a priority for Kicad's
developers: they got avhttp from a third party and did not modify it.
Avhttp comes with Boost license, which does not harm. However if you
take a look at
https://github.com/avplayer/avhttp/blob/master/CMakeLists.txt, you see
that it will try to link OpenSSL libraries, which are mandatory to
access Github now.

> Georges, did you post your build scripts somewhere public so I can do a local
> test build and cross-examine?

The full source package is the pool, see
http://debian.bononia.it/debian/pool/main/k/kicad/kicad_4.0.0~rc1-1.dsc

Thank you in advance for the help, I shall wait your response before
uploading the backport for Jessie. (the only difference is a build
dependency on boost1.55 rather than boost1.58)

Best regards,                   Georges.

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70

Attachment: signature.asc
Description: PGP signature

Reply via email to