Re: [Kicad-developers] bzr is unmaintained. Should we move KiCAD repository to git too?

[Povilas Kanapickas]

Just for the record, git has submodules feature, which allows to store
external dependencies in-tree and easily manage local patches to them.

Regards,
Povilas



___
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

Re: [Kicad-developers] Github Library repositories

[Carl Poirier]

A repository owner will want his copy-on-write directory to be the git
working directory, so that the updates to the libraries can be pushed
easily. Having the repositories ending in ".pretty" would make the default
folder naming during the git clone match the requirement.


On Sun, Dec 1, 2013 at 6:46 PM, Povilas Kanapickas  wrote:

> On 12/01/2013 11:45 PM, Carl Poirier wrote:
> > 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.
> >
>
> Looking at the code it seems that only local directories must have the
> .pretty suffix. There are no requirements on github repository names. In
> fact, they are not parsed in any way except to build an URL to fetch the
> contents of a repository.
>
> Regards,
> Povilas
>
>
> ___
> 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

Re: [Kicad-developers] Github Library repositories

[Povilas Kanapickas]

On 12/01/2013 11:45 PM, Carl Poirier wrote:
> 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
> .
> 
> 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.
> 

Looking at the code it seems that only local directories must have the
.pretty suffix. There are no requirements on github repository names. In
fact, they are not parsed in any way except to build an URL to fetch the
contents of a repository.

Regards,
Povilas


___
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

Re: [Kicad-developers] Github Library repositories

[Carl Poirier]

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
.

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 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@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

[Kicad-developers] Blueprint for "layouts as parts"

[Martin Janitschke]

Heyho,
I've created the blueprint [0] we've started to discuss in the "Next
Steps" thread. Comments are welcome :).
The blueprint partially supersedes [1] & [2] due to the fact that Pcbnew
will make it way easier to create panelized boards by hand and the
overhead to create the schematics for the whole board is now minimal.
(1. Add sub-sheets, assign the correct schematics, 2. select the correct
boards in CvPcb, 3. move the boards next to each other (without the old
hassle to select the whole board, move the already panelized boards out
of the way before appending the next one...)).
Bye,
imp

[0]: https://blueprints.launchpad.net/kicad/+spec/layouts-as-footprint
[1]: https://blueprints.launchpad.net/kicad/+spec/add-panelize-to-pcbnew
[2]: https://blueprints.launchpad.net/kicad/+spec/append-board

___
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