kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 4/3/2018 7:33 AM, jp charras wrote:
> Le 03/04/2018 à 13:25, Maciej Sumiński a écrit :
>> On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote:
>>> On 03/04/18 13:17, Nick Østergaard wrote:
>>>> I think we should not disable the github plugin, but we may need to
>>>> remove it from the wizard in a way that does not emphasize that this is
>>>> the way to go. Maybe it is ok to remove it completely from the wizard,
>>>> but just let the plugin in the fp-lib-table still work.
>>>
>>> I would rather disable it (with the possibility to re-enable in some
>>> config file for "hardcore" users). Over the last 3 years it brought us
>>> mostly troubles and no big advantage.
>>
>> I second that, the only potential issue we need to deal with is the
>> current plugin users. Once we remove the plugin, they will be stuck with
>> footprint libraries full of broken entries.
>>
>> For v6 we should simply provide a simple library updater taking
>> advantage of generic git interface (e.g. libgit), instead of tying
>> ourselves to Github.
>>
>> Cheers,
>> Orson
> 
> For V5, I was just talking about disabling github option in wizard only to avoid issue.
> The github plugin is an other story.

Please disable it in the wizard only to prevent users from using the
legacy libraries.  Disabling the plugin completely will break existing
users fp-lib-table entries which is not acceptable.  Until we can
provide some type of migration tool, we will have to leave the github
plugin enabled.  Hopefully over time, users will slowly migrate away
from using the github plugin.

> 
> In V6, we will need a library updater for symbol libs, footprint libs, 3d shapes libs, and perhaps
> some other things (python scripts for instance)
> 
> 

Maybe someone could create a git plugin to manage updating libraries.