kicad-developers team mailing list archive

[Carl Poirier <carl.poirier.2@xxxxxxxxx>]

OK, actually, I had not understood all of the copy-on-write functionality
of the GITHUB_PLUGIN, which Dick committed very recently.  Some information
about it can be read
here<http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/view/head:/pcbnew/github/github_plugin.h#L33>
.

Actually, we would need the repositories to end in ".pretty". This will
indicate at the same time that it's a pretty library, so no need for a
prefix.


On Sat, Nov 30, 2013 at 9:51 PM, Povilas Kanapickas <povilas@xxxxxxxx>wrote:

> On 11/30/2013 06:09 PM, Carl Poirier wrote:
> > While doing so, I was thinking that an alternative would have been to
> > create a second organization, named something like "KiCAD-Librairies",
> > to host them all and nothing else. In this case, maybe we could get rid
> > of the "_lib" prefix? I would personally prefer that, so our
> > fp-lib-table is even simpler. If any of you has an objection, please
> > voice in your input. Else, I'll run the script again for this new
> > organization, and hopefully make it the final library emplacement!
> >
>
> A prefix ensures that the repository structure is future proof. What if
> we decided to move symbol library repositories to Github too? This may
> result in slightly annoying ambiguities in certain usage cases.
>
> I think that in this case four characters isn't a big price to pay,
> especially when most of the library names are longer than 10 characters.
>
> By the way, what do you think about 'fp_' as a prefix? It's both more
> explicit and shorter.
>
> Regards,
> Povilas
>
>
>
>
>
> _______________________________________________
> 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
>