It's definitely technically possible for macOS--but as I'm continuing
to think about it, even if I whipped this patch up and tested it,
*and* I convinced enough people it worked, just thinking about all the
places in the docs where the macOS paths would have to change, I'm
thinking we *have* to wait.

Please let's get this in before V6...

Adam
On Wed, Jul 18, 2018 at 11:25 PM Seth Hillbrand <s...@hillbrand.org> wrote:
>
> It's a good idea but it's coming after we've already tagged v5.  Are we 
> thinking of a patch on the packaging?  I don't quite follow the proposal for 
> how this gets implemented.  For debian, we could place a patch in the build 
> package.  I assume that there is something similar for rpms but I'd be 
> curious to know how this would be implemented for Mac/Windows.
>
> -Seth
>
> Am Mi., 18. Juli 2018 um 21:08 Uhr schrieb Adam Wolf 
> <adamw...@feelslikeburning.com>:
>>
>> On Mac, we have the advantage of users not setting environment variables.  
>> This makes me think this *could* potentially be feasible for 5.0, for MacOS.
>>
>> However, I do not know if we would want this feature on one platform and not 
>> the others. Thoughts?
>>
>> On Mon, Jul 16, 2018, 12:40 PM Andy Peters <de...@latke.net> wrote:
>>>
>>> On Jul 16, 2018, at 10:22 AM, Mark Roszko <mark.ros...@gmail.com> wrote:
>>> >
>>> > Yea....thats what I proposed too.
>>> >
>>> > Every program on Windows that needs side-by-side installs just
>>> > versions both the config and install locations. Thats it.
>>> >
>>> > EAGLE does it.
>>> > Visual Studio does.
>>> > Altium does it.
>>> > CLion does it.
>>> > All of Jetbrains other product do it.
>>> > Microsoft Word does it
>>> > Adobe does it.
>>> > Python does it.
>>> > MSSQL does it.
>>> > <insert the hundreds of other programs in my start menu>
>>> >
>>> > No need for crazy launcher args and extreme actions such as doing
>>> > something like RVM does....
>>> >
>>> > All that needs to be done, is find all instances of wxStandardPaths
>>> > being used for config location.
>>> > Replace it with a standard static function helper. In the helper, it
>>> > appends a version number to the location.
>>> >
>>> > Thats it. Done. No need to require users to understand command line to
>>> > use a program.
>>> >
>>> > It works for linux too.
>>> > /home/user/.kicad/
>>> > becomes
>>> > /home/user/.kicad/5.1/
>>>
>>> And on the Mac that would be
>>>
>>> /Users/andy/Library/Application Support/kicad
>>>
>>> becomes
>>>
>>> /Users/andy/Library/Application Support/kicad/5.1
>>>
>>> and /Users/andy/Library/Preferences/kicad
>>>
>>> becomes
>>>
>>> /Users/andy/Library/Preferences/kicad/5.1
>>>
>>> -a
>>
>> _______________________________________________
>> 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

Reply via email to