Hi Simon, Wayne,
> If they have local work, the sanest approach is to rebase on top of
> origin/master and delete the offending commits at the same time by doing
> an interactive rebase
>
> $ git rebase -i origin/master
>
> This gives a list of all commits that don't have identical content i
Hi Wayne,
I just tried the remapping tool as well, and wanted to share some
thoughts on it. This e-mail, where you're explaining how the remapping
process works seemed like an appropriate place to reply.
I tested this two weeks ago, using the 2017-12-22 daily build ppa, but
didn't get around to w
Hi Wayne,
> The symlink issue has been fixed so duplicate libraries will not show up
> in the project symbol library table with different nicknames.
I noticed some issues with my previous build (2017-12-22), but using the
2018-01-03 build, symlinks (both in the directory and filename) indeed
seem
Hi Wayne,
> >> If the remapping algorithm cannot find the exact library match which
> >> is currently being used (and should be in the project library list or
> >> the cache) to provide the symbol, then there is no way to determine
> >> the correct library and therefore cannot be remapped. It als
Hey Rene,
> This is not as easy as simply a one to one mapping. The connectors
> library has been split into 3 libs. Most other libs into even more.
> (Especially manufacturer specific libs.)
> In reality the best option for old projects will be to have the v4 libs
> installed in addition to the n
Hi folks,
> > 3. What are the plans for providing coherent library names and the
> > introducing new libraries?
> We will try to limit such problems. But it might still happen that a library
> will be split up into multiple libs if the library gets too large.
I had an idea on solving this. Not sur
Hi Wayne,
> KiCad should not be determining which libraries get loaded just because
> our library layout gets more complex. I would reject any design changed
> that loaded libraries outside the users control. Maybe I'm misreading
> this but it kind of sounds like that to me.
My proposal would in
Hi Wayne, Carsten,
On Mon, Jan 15, 2018 at 12:49:00PM -0500, Wayne Stambaugh wrote:
> I agree 100%. Once we tag the v5 stable libraries, package devs should
> clone from that version for every v5 point release to prevent the issue
> you are describing.
I think there might be a misunderstanding h
Hi Maciej,
> I can easily imagine a message saying: "Why do you guys modify my
> perfectly organized symbol library table when I update the libraries
> package? I have carefully picked the libraries that are useful to me, so
> I do not need to go through a long list when selecting components. Now
Hi Wayne,
> > > [Proposal to make library upgrades easier]
> >
> > As a user, 1% agree.
>
> Me too! If users want to constantly update their libraries, that's
> their choice but kicad installers should not be forcing this on users.
> We should have a fixed set of libraries that are tagged for
Hi Wayne,
> I was not being sarcastic. Here is what I meant:
Thanks for clarifying.
> For stable version 5, the libraries should be tagged and used for all
> stable 5 point releases (5.0.1, 5.0.2, ...). Most corporate users
> prefer consistency over having the latest libraries so installing the
Hi Wayne,
> This is not a trivial issue to fix. I'm not sure there is a good answer
> for this issue.
It's certainly not trivial, but I believe a fix would not be terribly
hard either.
Let me repeat my original proposal here:
> I can imagine that KiCad either gets a way to:
> 1) include all li
Hi Carsten,
it seems this ties in what an earlier proposal I did, see this post (and
the followup discussion):
https://lists.launchpad.net/kicad-developers/msg33224.html
My proposal was to ship a (fp|sym)-lib-table file along with library
packages, and then (explicitly) include that from the main
Hey folks,
I've been trying to update to the latest nightly build, but it seems
that the PPA has stopped building version for artful (17.10). The latest
version is:
kicad 201807190649+829ba27~83~ubuntu17.10.1 js-reynaud (2018-07-19)
(from https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad
Hey folks,
> I've been trying to update to the latest nightly build, but it seems
> that the PPA has stopped building version for artful (17.10).
Seems the same thing happens for the kicad-5 release PPA (it has only
5.0.0 for Artful). For the kicad-5-nightly PPA, no artful builds are
available at
Hi Jean-Samuel,
> Launchpad doesn't support anymore build for artful. So it will no more
> available.
Ah, that explains. A quick google for this didn't turn up any info, but
I should probably have dug a bit deeper.
> Have you try Xenial PPA ? (not sure if it's working...)
Hm, I recall I moved to
16 matches
Mail list logo
