[Kicad-developers] Gitlab CI sucks

2020-04-24 Thread Nick Østergaard
Hello

Everything new is hard. I fell quite a bit frustrated by the pipeline scripts.

https://gitlab.com/kicad/services/kicad-doc/pipelines/139696624

Someone with some more experience please propose a better merge
request that will not unconditionally push to the registry, and
trigger downstream projects.

It is getting late here.

Nick Østergaard

p.s. Not in a good mude, but I guess it is better to send this now
than later. Sorry if I hurt anyone, it is not intentional.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] Separate download server directory for each Windows nightly build installer version?

2020-04-24 Thread Nick Østergaard
I don't think we gain anything for adding more directories.

As Andrew suggested, it is probably better to make a script or helper
tool for yourself to do that. You may be able to use aws s3 or s3cmd
to query the server.

On Fri, 24 Apr 2020 at 22:58, Andrew Lutsenko  wrote:
>
> If you do something daily then why not automate it?
> A simple shell or python script will do the job and use much less ram than a 
> browser tab :)
>
> On Fri, Apr 24, 2020 at 1:10 PM Eeli Kaikkonen  
> wrote:
>>
>> I keep the Windows nightly build download server page 
>> (https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/nightly/) open 
>> in a browser tab to download the latest nightly build, often daily. It's 
>> slightly annoying to have four files for each nightly build: 64 and 32 bit, 
>> and lite and full.
>>
>> Could it be possible to have four directories under the main directory:
>> * full_installer_with_libraries_64bit
>> * full_installer_with_libraries_32bit
>> * lite_installer_downloadable_libraries_64bit
>> * lite_installer_downloadable_libraries_32bit
>>
>> Then I could just refresh the tab and click on the last file. Now I have to 
>> check every time which one is what I want so that I don't download a wrong 
>> one by accident (which has happened).
>>
>> (The same is of course true for the 5.1 testing builds.)
>>
>> Eeli Kaikkonen
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] Separate download server directory for each Windows nightly build installer version?

2020-04-24 Thread Andrew Lutsenko
If you do something daily then why not automate it?
A simple shell or python script will do the job and use much less ram than
a browser tab :)

On Fri, Apr 24, 2020 at 1:10 PM Eeli Kaikkonen 
wrote:

> I keep the Windows nightly build download server page (
> https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/nightly/)
> open in a browser tab to download the latest nightly build, often daily.
> It's slightly annoying to have four files for each nightly build: 64 and 32
> bit, and lite and full.
>
> Could it be possible to have four directories under the main directory:
> * full_installer_with_libraries_64bit
> * full_installer_with_libraries_32bit
> * lite_installer_downloadable_libraries_64bit
> * lite_installer_downloadable_libraries_32bit
>
> Then I could just refresh the tab and click on the last file. Now I have
> to check every time which one is what I want so that I don't download a
> wrong one by accident (which has happened).
>
> (The same is of course true for the 5.1 testing builds.)
>
> Eeli Kaikkonen
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


[Kicad-developers] Separate download server directory for each Windows nightly build installer version?

2020-04-24 Thread Eeli Kaikkonen
I keep the Windows nightly build download server page (
https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/nightly/) open
in a browser tab to download the latest nightly build, often daily. It's
slightly annoying to have four files for each nightly build: 64 and 32 bit,
and lite and full.

Could it be possible to have four directories under the main directory:
* full_installer_with_libraries_64bit
* full_installer_with_libraries_32bit
* lite_installer_downloadable_libraries_64bit
* lite_installer_downloadable_libraries_32bit

Then I could just refresh the tab and click on the last file. Now I have to
check every time which one is what I want so that I don't download a wrong
one by accident (which has happened).

(The same is of course true for the 5.1 testing builds.)

Eeli Kaikkonen
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


[Kicad-developers] Submitting new wizards and plugins

2020-04-24 Thread Alan Samet
Please excuse me if this has been asked before or it's in a FAQ somewhere
that I haven't located. 

 

I've written a number of scripts for KiCad over the past few months for
things like component alignment and spacing, and am now working on
converting those to plugins and additional footprint wizards. I feel like
the community could benefit from some of these tools, but I don't know the
best way to submit them or if these sorts of things are welcomed by the
community. For the new footprint wizards, for instance, should I just submit
a pull-request to github of the kicad-footprint-wizards project? 

 

-Alan

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] Is it really the case that installing KiCad on a Mac requires manually copying files around?

2020-04-24 Thread Nick Østergaard
Just a small comment. The windows that Adam attached are actually
Finder, the file explorer thing on macos, that is stylized as part of
the Disk Image file (.dmg). Hence, when the user do the "drag the
KiCad folder to Applications" it is just a  normal file copy. It just
happens that apple peeps "like" to drag things instead of clicking
next.

On Fri, 24 Apr 2020 at 17:35, Michael Kavanagh
 wrote:
>
> This is completely standard. Infact, the .pkg installers that Jon
> mentioned are in my experience very rare (only Microsoft Office and
> MatLab initially spring to mind).
>
> On Fri, 24 Apr 2020 at 15:22, Rene Pöschl  wrote:
> >
> > Hi all but especially adam,
> >
> >
> > lately there where a few threads on the forum where installation on Mac
> > came up. The users reported that they installed KiCad by manually
> > copying files around which sounded wrong to me. But as a lot of users
> > seem to be under the impression that this is indeed the right way i am
> > now starting to believe them.
> >
> > If these users are really correct then maybe this should be documented
> > very clearly on our download page. Or if there is any option to automate
> > this process (reducing human error) then maybe this would be the better
> > way to go long term but until then it should still be documented what
> > needs to be copied.
> >
> > One problem i see is if users can copy KiCad files then the libs might
> > not be write protected which would be a problem as KiCad relies on the
> > operating system write protection to avoid users modifying the shipped
> > libraries.
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] Is it really the case that installing KiCad on a Mac requires manually copying files around?

2020-04-24 Thread Michael Kavanagh
This is completely standard. Infact, the .pkg installers that Jon
mentioned are in my experience very rare (only Microsoft Office and
MatLab initially spring to mind).

On Fri, 24 Apr 2020 at 15:22, Rene Pöschl  wrote:
>
> Hi all but especially adam,
>
>
> lately there where a few threads on the forum where installation on Mac
> came up. The users reported that they installed KiCad by manually
> copying files around which sounded wrong to me. But as a lot of users
> seem to be under the impression that this is indeed the right way i am
> now starting to believe them.
>
> If these users are really correct then maybe this should be documented
> very clearly on our download page. Or if there is any option to automate
> this process (reducing human error) then maybe this would be the better
> way to go long term but until then it should still be documented what
> needs to be copied.
>
> One problem i see is if users can copy KiCad files then the libs might
> not be write protected which would be a problem as KiCad relies on the
> operating system write protection to avoid users modifying the shipped
> libraries.
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] Is it really the case that installing KiCad on a Mac requires manually copying files around?

2020-04-24 Thread Jon Evans
I believe these users are talking about the normal MacOS method of
installing software,
which does typically involve copying files.

Normally MacOS software is packaged as a disk image that is mounted when
you double click it.

The mounted image then normally contains the software to be installed, and
shortcuts
that are used as drop targets for a "drag and drop" copy.

Most software only has one "file" (the .app file, which is actually a
directory)
That file is copied to the Applications folder on the user's system.

KiCad's installation also involves copying a second folder to a privileged
location (Application Support),
so the user will be prompted for authentication when they do this step.

This part of the approach is not very common for commercial MacOS software.
Software that must install to privileged locations typically ships as a
binary installer with a wizard,
more like what you would typically see on a Windows machine.

I am not familiar enough with the MacOS packaging to know if there is any
potential for KiCad
to have a single app file that just gets copied to Applications in the
future.

If we want to do fancy things such as write-protecting certain parts,
probably the best bet would be to build a MacOS installer wizard (a PKG
file).
But, I don't know the details there either or if there are reasons we
cannot / should not.

-Jon

On Fri, Apr 24, 2020 at 10:22 AM Rene Pöschl  wrote:

> Hi all but especially adam,
>
>
> lately there where a few threads on the forum where installation on Mac
> came up. The users reported that they installed KiCad by manually
> copying files around which sounded wrong to me. But as a lot of users
> seem to be under the impression that this is indeed the right way i am
> now starting to believe them.
>
> If these users are really correct then maybe this should be documented
> very clearly on our download page. Or if there is any option to automate
> this process (reducing human error) then maybe this would be the better
> way to go long term but until then it should still be documented what
> needs to be copied.
>
> One problem i see is if users can copy KiCad files then the libs might
> not be write protected which would be a problem as KiCad relies on the
> operating system write protection to avoid users modifying the shipped
> libraries.
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


[Kicad-developers] Is it really the case that installing KiCad on a Mac requires manually copying files around?

2020-04-24 Thread Rene Pöschl

Hi all but especially adam,


lately there where a few threads on the forum where installation on Mac 
came up. The users reported that they installed KiCad by manually 
copying files around which sounded wrong to me. But as a lot of users 
seem to be under the impression that this is indeed the right way i am 
now starting to believe them.


If these users are really correct then maybe this should be documented 
very clearly on our download page. Or if there is any option to automate 
this process (reducing human error) then maybe this would be the better 
way to go long term but until then it should still be documented what 
needs to be copied.


One problem i see is if users can copy KiCad files then the libs might 
not be write protected which would be a problem as KiCad relies on the 
operating system write protection to avoid users modifying the shipped 
libraries.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp