Electronics > KiCad
KiCAD 7.0.1 released
nimish:
--- Quote from: ve7xen on March 20, 2023, 07:51:59 pm ---Why 'without their awful builder hack'? As much as its existence and/or necessity may annoy you, doesn't it make sense to use the same build tooling used by the project's other developers and release pipeline? Improving the build process is a laudable goal in itself, but you don't seem interested in that, so why not just use the existing tooling?
--- End quote ---
I did attempt to use their documented process and then debugged it after it failed. I've shot off some minor MR's to make that happen less which may help fix it for others.
I have a private fork with both internal proprietary changes to work with custom CI/CD as well as other, open-sourceable, ones that do fix the issue. If the latter changes can be upstreamed, I'm happy to upstream them.
--- Quote ---If a major revision takes place its common in software to add in version data converters.
Like V6 to V7 that converts all the file formats accordingly.
--- End quote ---
The issue for me is going the other way and least surprise: you want to know if running Kicad on data will change it meaningfully. Automating this with python usually handles it for me, but it'd be nice not to have to do that. Some projects make a point of maintaining compatibility, some projects don't.
The KiCad NGSPICE integration is pretty good. You use KiCad as the schematic capture for the spice sim. You do have to make sure components have proper SPICE models. It's a lot nicer than LTSpice IMO.
Ranayna:
The Arch based Manjaro offered the new KiCAD in the latest group of updates. I installed it, because i have not done much, if anything, with KiCAD in the last year.
But now i am a bit curious. I am relatively new to Linux as a daily driver, and until now i always just installed everything that the updater presented.
How should i have proceeded if, for compatibility reasons, i would not want to upgrade KiCAD? It was just a single entry in a large list of hundreds of updates, i could easily have missed it.
How would i do a downgrade? Looking for KiCAD in the repository only shows the latest version.
retiredfeline:
Preventing updates is something that's done in your packaging system. Typically you lock a package from being updated. Details depend on your distro.
Downgrading is also a function of the packaging system. Typically you have to tell it to let you override the stipulation that versions must increase.
But beware, you cannot go backwards on projects that have been converted to a higher version. So keep snapshots of projects and/or work on copies when you upgrade your project, in case you need to go back.
ve7xen:
--- Quote from: Ranayna on April 03, 2023, 08:59:24 am ---The Arch based Manjaro offered the new KiCAD in the latest group of updates. I installed it, because i have not done much, if anything, with KiCAD in the last year.
But now i am a bit curious. I am relatively new to Linux as a daily driver, and until now i always just installed everything that the updater presented.
How should i have proceeded if, for compatibility reasons, i would not want to upgrade KiCAD? It was just a single entry in a large list of hundreds of updates, i could easily have missed it.
How would i do a downgrade? Looking for KiCAD in the repository only shows the latest version.
--- End quote ---
See IgnorePkg in /etc/pacman.conf for the 'basic' approach to this. It will just prevent the KiCad package from ever being upgraded. Unfortunately I don't think there's a way to pin a semantic version match (e.g. take all 7.x.x upgrades but don't upgrade to 8.x.x).
However it's likely this won't work forever, as the rest of the system gets updated around it, either this pinning will prevent upgrades of the system or it will just stop working (not sure whether Pacman resolves/checks dependencies for Ignored packages).
Arch sometimes gets people configuring AUR builds based on older releases, if the demand is high enough.
Another way you can approach this is using the Flatpak, which should be self contained, so less likely to break as the system updates around it. See flatpak-mask.
Generally speaking, this is 'downside' of running a rolling release, even if you pin your software version, they will break eventually.
Reckless:
How does KiCad compare to Altium? I want a simple software that doesn't require hours and hours of training to get comfortable with. Easyeda looks pretty simple to use.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version