← Back to team overview

kicad-developers team mailing list archive

Re: 5.1.4 release - release announcement/blog entry?

 

When I tested this, notarization didn't exist, and I think it's a subset of
what we need for signing.  We may be able to notarize now, actually!

Adam

On Tue, Aug 13, 2019, 5:21 PM Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>
wrote:

> Yes, I did… and I still don’t really like this multi-application approach.
> To be honest, I never tried to notarize something and I haven’t read very
> much about it.
>
> Did you try to notarize the complete package/dmg including symlinks?
>
> Or, only kicad.app on its own (without symlinks and all other stuff) and
> then just put the signed kicad.app and the symlinks into the dmg afterwards?
> I just tried to create a symlink to Instruments inside Xcode and nothing
> complains when launching it via symlink.
> I don’t know if it would satisfy Gatekeeper, but the dmg just as container
> shouldn’t need any notarizing?
>
>
> Bernhard
>
> > On 14. Aug 2019, at 00:10, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
> >
> > Oh hey, Bernhard, I didn't see it was you... yeah, you know what I'm
> > talking about since you wrote a bunch of this CMake stuff, didn't you?
> > :)
> >
> > Adam
> >
> > On Tue, Aug 13, 2019 at 5:06 PM Bernhard Stegmaier
> > <stegmaier@xxxxxxxxxxxxx> wrote:
> >>
> >> I see, the symlinks… yes, haven’t seen anything like that elsewhere.
> >>
> >> On 14. Aug 2019, at 00:02, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
> >>
> >> I spent quite a long time on this maybe 18 months ago.  After I did a
> lot on my own, I was told by a few sources, one at Apple, that due to our
> symlinks, files were belonging to more than one .app, and it wasn't going
> to work.
> >>
> >> Things may have changed, and they may have been wrong, so feel free to
> work on it again, but I really suspect the easiest way out is to make a
> better launcher that'll open the correct subapplication based on the
> argument/drop target.
> >>
> >> On Tue, Aug 13, 2019, 4:54 PM Bernhard Stegmaier <
> stegmaier@xxxxxxxxxxxxx> wrote:
> >>>
> >>> What’s the problem with signing it?
> >>> Xcode also has applications inside its main bundle and I guess it is
> signed?
> >>>
> >>> Regards,
> >>> Bernhard
> >>>
> >>>> On 13. Aug 2019, at 21:53, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
> >>>>
> >>>> Builds can't be signed until
> >>>> https://bugs.launchpad.net/kicad/+bug/1826649. I have everything in
> >>>> place once that is complete.
> >>>>
> >>>> Adam
> >>>>
> >>>> On Tue, Aug 13, 2019 at 1:34 PM Andy Peters <devel@xxxxxxxxx> wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On Aug 13, 2019, at 10:57 AM, Adam Wolf <
> adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
> >>>>>>
> >>>>>> macOS is ready!
> >>>>>
> >>>>> Hola — downloaded and installed it, and got the complaint about
> “unidentified developer.” I know how to work around that, but I thought the
> builds were signed so the complaint doesn’t pop up?
> >>>>>
> >>>>> -a
> >>>>> _______________________________________________
> >>>>> 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
> >>>
> >>
>
>

Follow ups

References