Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

After considering my patch, what about the following proposal: Just change the hard coded string in common.cpp (at around line 243) from: cfgpath.AppendDir( wxT( "kicad" ) ); to cfgpath.AppendDir( wxT( "kicad.v5" ) ); (or some other string) Thats it.  Then Kicad Version 5 will have a unique

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

I would pretty much vote to use the IMO more common naming scheme for major package versions: kicad (the current one installed from the repository of your choice) kicad4 (currently: 4.0.7) kicad5 (currently: 5.0.0-rc2-dev...) kicad6 (tbd.) ...avoiding the ".v5" i've seen lately. I believe

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Hi, Am 12.04.2018 um 15:47 schrieb Reece R. Pollack: > I'm a relative newbie to KiCad, but I've been a software engineer since > the early 1980. I'd prefer to see KiCad installed in a self-contained > manner, meaning all installed files end up under one directory hierarchy > rather than being

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

On 12/04/18 21:49, Jean-Samuel Reynaud wrote: Perhaps this name should be configurable ("overridable" ?) by an env variable ? Yes I think so too.  We have two proposals so far, an environment variable, or a command line switch.  Either or both would work.  But both are creeping the scope and

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

kicad5 kicad6 etc etc works for me.  I am not wedded to my suggestion, it was illustrative only. For backward compatibility, "kicad" would be for kicad4 because that's what it uses now, so there would be no "kicad4". I agree that a user selectable configuration directory would be useful

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Perhaps this name should be configurable ("overridable" ?) by an env variable ? Le 12/04/2018 à 15:29, Strontium a écrit : > kicad5 > kicad6 > etc etc works for me.  I am not wedded to my suggestion, it was > illustrative only. > > For backward compatibility, "kicad" would be for kicad4 because

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

I'm a relative newbie to KiCad, but I've been a software engineer since the early 1980. I'd prefer to see KiCad installed in a self-contained manner, meaning all installed files end up under one directory hierarchy rather than being spread all over the filesystem. This is how Xilinx ISE,

[Kicad-developers] Jenkins build is back to normal : kicad-qa #3930

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

[Kicad-developers] Build failed in Jenkins: kicad-qa #3929

See Changes: [tomasz.wlostowski] pcbnew: refresh message panel while drawing & editing graphical lines, -- [...truncated 1.12 KB...] > git rev-list --no-walk

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Den tor. 12. apr. 2018 17.18 skrev Reece R. Pollack : > On 04/12/18 09:58, Carsten Schoenert wrote: > > Hi, > > Am 12.04.2018 um 15:47 schrieb Reece R. Pollack: > > I'm a relative newbie to KiCad, but I've been a software engineer since > the early 1980. I'd prefer to see KiCad

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Am 12.04.18 um 18:33 schrieb Reece R. Pollack: > Yes, I'm going a bit off the original topic. Maybe we should start a new > thread. But I see an issue arising in the future where people are going > to want to install V5 but not give up V4 quite yet. For example, board > houses that accept

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Is it usefull ? Yes! Thank you ver much. I like to report bugs against nightly but don’t always have time to compile and I need a fairly stable KiCad for other work. I switched away from your daily ppa (ppa-kicad) since the schematic lib table changes hit because I didn’t have time to deal with

[Kicad-developers] Build failed in Jenkins: kicad-qa #3928

See Changes: [Maciej Suminski] Added std::less specialization for wxPoint [Maciej Suminski] Eagle SCH import: improved implicit connections resolution -- Started by an SCM change

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

On 04/12/18 11:38, Nick Østergaard wrote: Den tor. 12. apr. 2018 17.18 skrev Reece R. Pollack >: On 04/12/18 09:58, Carsten Schoenert wrote: Hi, Am 12.04.2018 um 15:47 schrieb Reece R. Pollack: I'm a relative newbie to KiCad, but I've

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Am 12.04.18 um 17:18 schrieb Reece R. Pollack: > The KiCad 4.0.7 Debian Linux package installs files in these directories: > > /etc/profile.d > /usr/bin > /usr/lib/kicad > /usr/lib/python2.7/dist-packages > /usr/share/applications > /usr/share/doc > /usr/share/icons > /usr/share/kicad >

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

I have just been observing this thread for a while and I’m wondering if (at least for *nix implementations) installing the files into a version specific sub-tree and putting links into the “unix/linux way” directories might be a solution - having a simple script change the links to enable a

[Kicad-developers] Why are courtyard rules not saved in the board?

Not the courtyard graphics, but rather the require-courtyards and no-overlapping-courtyard settings? ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

On 04/12/18 09:58, Carsten Schoenert wrote: Hi, Am 12.04.2018 um 15:47 schrieb Reece R. Pollack: I'm a relative newbie to KiCad, but I've been a software engineer since the early 1980. I'd prefer to see KiCad installed in a self-contained manner, meaning all installed files end up under one