← Back to team overview

kicad-developers team mailing list archive

Re: GitHub Plugin (my nemesis)


Sorry if I don't get it.. Why not just ask the user for a working directory and pull the libraries there using actual git? 
This has the obvious advantage, that anyone can use this not only with github but also with his or her own local repository.. 
Then maybe later add more functionality, such as the proposed visual diff or even a simple button to update specific libs from git remote by request of the user.. 

Best regards 

Am 22. September 2017 03:21:27 MESZ schrieb Oliver Walters <oliver.henry.walters@xxxxxxxxx>:
>Hi all,
>Ok, now that the website integration with the libraries is (pretty
>done, and the licensing issue seems to be sorted, there is one final
>piece to solve before I'm happy with the state of the libraries for a
>*Goal: *Merge all footprint library repositories into a single repo to
>solve the ongoing dramas of maintaining 100+ repos.
>*Problem*: The *only* thing standing in the way of just doing this is
>some users like the GitHub plugin and previous instruction is that this
>functionality cannot be removed.
>The GitHub plugin functions by downloading a .zip file of a .pretty
>If we merge all footprint libs into a single repo with multiple
>subdirectories, this will not work anymore (as GitHub dosen't allow you
>download a .zip of a single subdirectory).
>Merging the repos is the *right thing to do*. But how to proceed?
>*a) Drop github plugin feature, replace with library-download tool*
>I don't think it is a good idea to live-load library data from GitHub
>lot of other users agree too). It's slow, and a waste of bandwidth to
>re-download the libs all the time.
>We drop support for loading libraries direct from GitHub. However, we
>add a
>tool for downloading libraries from GitHub and storing to disk. Users
>update as they like. This can be integrated in KiCad and new users can
>this tool when they first install KICad. This means that no libs need
>distributed with the installer and users can update to latest libs
>they want.
>*b) Improve github plugin to allow subdirectory traversal*
>This is difficult and will only result in the plugin being slower.
>are two ways I can see to do this:
>i. Use Git API - tools exist that use this functionality -
>ii. Use subversion - GitHub actually provides subversion API -
>In either case, I think that using the subversion tool to partially
>download the libraries would be a good approach (I assume quicker than
>using wget and the GitHub API).
>1. Does anyone have any experience using the C API for SVN?
>2. The Python bindings are pretty good -
>https://pypi.python.org/pypi/svn -
>and much easier to use. However, can we make the library download tools
>dependent on enabling the python plugin?
>3. Is there a way to checkout a subversion remote to memory (to
>the functionality of the current GitHub plugin)? If not, I'm not sure
>to approach option b) above.
>Feedback appreciated. I think that it is very important especially for
>users that this is improved. The GitHub plugin is constantly causing

Follow ups