stretch install no hostmot2 in synaptic
I'm not that aware of, how to change the wiki works right now, lot's of moons have past since I did that last time.
But I'll have a look at that.
I suspect it could be added somewhat automatically if the right repository stanza was present (the firmware is independent of OS/version etc)
Which repository has the firmware?
jgnoss wrote: John a question completely OT
Not so long ago on the dev forum you posted a link to a work done implementing a plasma cutter GUI using QTVCP
Do you mind giving me that link here again, I like to have a closer look at that.
I do think your mistaken about the GUI, you might be thinking about my QtPyVCP plasma gui... github.com/jethornton/plasma_v2
But then Mesa moved on to newer FPGAs using a different Xilinx ISE and the LinuxCNC build system couldn't build the newer firmwares.
This is certainly something that we need to consider when making the next LinuxCNC LiveCD (2.8 release)
It might not matter that the LinuxCNC packager can't build the new firmwares, as the new cards don't need to load the firmware on every boot. Only the legacy cards (5i20, 5i23, 7i43 etc) need the firmware to be resident in /lib/firmware to be able to boot.
I don't know how it is, if someone makes a fresh install and then try to configure the system from scratch using pncconf.
The time I switched from 2.really_old to 2.8_pre I did that on a fresh installed wheezy machine. I started to convert my .ini and .hal by hand but give up on that and tried to use pncconf to get a clean base config to start on. Trying that I have had the firmware problem too, but it was as simple as apt install hostmot2 to solve the problem.
I don't know how hard it is to create a let's say "hostmot2_lagecy" package that does just install that legacy firmware on the system.
jgnoss wrote: I don't know how hard it is to create a let's say "hostmot2_lagecy" package that does just install that legacy firmware on the system.
Well, the package manager needs to have a link to the server, and the server needs to exist to serve the package.
So it requires both synaptic to be aware of the server, and someone to host and pay for the server, keeping it updated for each new debian (and other distro?) version.