You are not logged in.
I happened to visit KICON 2025 Europe, because of using KiCad software.
The training used Version 9 so I installed from Backports.
dpkg -l kicad
ii kicad 9.0.3+dfsg-1~bpo12+1 amd64 Electronic schematic and PCB design software
This removed
zgrep -i kicad dpkg.log.2.gz
...
2025-07-09 10:35:09 remove kicad-packages3d:all 6.0.10-1
...
In the KiCad training I learnt, that other operating systems support different versions of the same Software on the same host.
That will be needed to maintain older pcb Hardware.
Under debian the new versions kick out the old versions.
The debian maintainer answered, that he does not intend to change this behavior.
Commercial use with debian/devuan is such not possible. You do not want to migrate old projects forcefully to new versions, for small changes in a maintenance phase. Migration is not backwards compatible.
KiCad supports flatpak officially but only a "stable" version, which is changing every year.
What can be done ?
The devil, you know, is better than the angel, you don't know. by a British Citizen, I don't know too good.
One generation abandons the enterprises of another like stranded vessels. By Henry David Thoreau, WALDEN, Economy. Line 236 (Gutenberg text Version)
broken by design :
https://bugs.debian.org/cgi-bin/bugrepo … bug=958390
Offline
found a few articles/commentaries/guides/etc but haven't read them yet:
(providing them here for the convenience of all)
Be Excellent to each other and Party On!
https://www.youtube.com/watch?v=rph_1DODXDU
https://en.wikipedia.org/wiki/Bill_%26_Ted%27s_Excellent_Adventure
Do unto others as you would have them do instantaneously back to you!
Offline
That will be needed to maintain older pcb Hardware.
Under debian the new versions kick out the old versions.
The debian maintainer answered, that he does not intend to change this behavior.
Commercial use with debian/devuan is such not possible. You do not want to migrate old projects forcefully to new versions, for small changes in a maintenance phase. Migration is not backwards compatible.
I think all Linux distributions will do the same: kick out the old versions.
The kicad documentation states that a project once modified can no more be read by an older version of kicad. But does that mean the design data is screwed up?
If you are very conservative and precautios, make up a VM with the older kicad version.
Anyhow: on the kicad home page I can't find any support for downloading older versions either.
Last edited by rolfie (Yesterday 12:10:04)
Offline
The kicad documentation states that a project once modified can no more be read by an older version of kicad. But does that mean the design data is screwed up?
Definitely yes as said by trainer. Killer.
Anyhow: on the kicad home page I can't find any support for downloading older versions either.
So do I, asking with the KiCad people right now.
Flatpak support is stated below on their website, a new field of distraction.
The devil, you know, is better than the angel, you don't know. by a British Citizen, I don't know too good.
One generation abandons the enterprises of another like stranded vessels. By Henry David Thoreau, WALDEN, Economy. Line 236 (Gutenberg text Version)
broken by design :
https://bugs.debian.org/cgi-bin/bugrepo … bug=958390
Offline
You might be better off trying an appimage, a quick search shows them available in kicad versions 6,7,8, and 9.
https://sourceforge.net/projects/vuu-do/ New Vuu-do isos uploaded August 2025!
Vuu-do GNU/Linux, minimal Devuan-based Openbox and Mate systems to build on. Also a max version for OB.
Devuan 5 mate-mini iso, pure Devuan, 100% no-vuu-do. Devuan 6 version also available for testing.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
Offline
Either the appimage as mentioned or compiling your own version using perhaps /usr/local/bin as the place for the binary and an edit possibly of the make file to change the binary name to something like kicad7 for version7 for the new name to prevent confusion in running it.
Offline
/usr/local/bin is the standard solution.
cmake -D CMAKE_INSTALL_PREFIX=/usr/local < + other options: -S (sourcedir), etc.>
However, debhelper (Devuan) does not permit /usr/local/bin (though there might be a "secret option").
In any case, it is much easier to package it manually, or with CPack .
You may want to rename the deb package, and ProjectName
project( ) is inside CMakeLists.txt
To compile it, you need cmake and ninja
Portable CMake is available here:
_https://github.com/Kitware/CMake
Portable Ninja is available here:
_https://github.com/ninja-build/ninja
PKGBUILD:
build() { cmake \ -B build \ -S "$pkgname" \ -G Ninja \ -D CMAKE_BUILD_TYPE=Release \ -D CMAKE_INSTALL_PREFIX=/usr \ -D KICAD_USE_EGL=ON \ -D KICAD_USE_BUNDLED_GLEW=OFF \ -D KICAD_BUILD_I18N=ON \ -D KICAD_I18N_UNIX_STRICT_PATH=ON \ -D KICAD_BUILD_QA_TESTS=OFF \ -D KICAD_USE_CMAKE_FINDPROTOBUF=0 \ -W no-dev cmake --build build } package() { DESTDIR="$pkgdir" cmake --install build strip "$STRIP_SHARED" "${pkgdir}"/usr/lib/python*/site-packages/_pcbnew.so }
_https://archlinux.org/packages/extra/x86_64/kicad/
_https://gitlab.archlinux.org/archlinux/packaging/packages/kicad
_https://gitlab.archlinux.org/archlinux/packaging/packages/kicad/-/blob/main/PKGBUILD?ref_type=heads
EXAMPLE for cmake+ninja
_https://dev1galaxy.org/viewtopic.php?id=7175
Last edited by igorzwx (Today 01:43:25)
Offline