kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

I'll try to clarify the options that I see.

1) Store the libraries *inside* the bundle, in kicad.app.  Users should
never change these, because if they do, the changes would be lost when you
update KiCad.
2) Have the libraries be included in the DMG, but users would have to drag
Kicad into Applications and Libraries into ~/LibraryApplication\
Support/whever/it/is/supposed/to/be, but we would have two symlinks, and a
background image on the DMG to make it obvious what to do.
3) Have two DMGs, one with just Kicad, one with just Libraries.  This would
be almost the same as #2.

Thoughts, folks?  I am personally leaning towards 2.  One thing to
download, but nothing stored inside kicad.app except for the KiCad
executables...

Adam Wolf
Cofounder and Engineer

On Thu, Nov 6, 2014 at 12:59 PM, Andy Peters <devel@xxxxxxxxx> wrote:

>
> > On Nov 6, 2014, at 11:51 AM, Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>
> wrote:
> >
> > Yes, one .dmg is also fine with me.
> >
> > We shouldn’t put anything into the bundle that a user can change (like
> adding his own symbol to a predefined library, etc.).
> > If the changes are stored in files inside the bundle itself then they
> will just get lost when a user tries to update the usual way (delete old
> from /Applications, drag new one into it).
> >
> > That would really be frustrating I guess...
>
> Very frustrating indeed. Why an application would store what is
> essentially user data in an opaque bundle is beyond me (see iPhoto, for
> example) ...
>
> -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
>