Hi all, does anyone know if it is possible to install EasyEDA on Fedora40-workstation.
This is an electronic design program it only has an AppImage for linux.
Can this be used in Fedora?
Thanks
Regards
Charles
Hi all, does anyone know if it is possible to install EasyEDA on Fedora40-workstation.
This is an electronic design program it only has an AppImage for linux.
Can this be used in Fedora?
Thanks
Regards
Charles
Downloading the EasyEDA file and then extracting it reveals a “how to install” txt file.
Following those instructions gets the App installed …
Cheers.
For managing appimages I highly recommend to use some tool to make this reasonably secure.
Some appimages may have an updater process and implementation (usinf zsync) but most will not.
You shouldnt just download random stuff from websites, put it somewhere and done.
I heard AppMan is really good for this.
Alternatively there is GearLever.
This is not just a random appimage, Easyeda is a trusted source, I have been using their software for quite a number of years (on windows).
As noted, inside their “extracted” folder is a “how to install” file with a bash command that needs to be run for install to happen.
Thank you for the heads up on appimages though, as I have heard bad things can happen. I will certainly look into the suggested software.
Thank you.
Regards
Charles
The issue lies in
In theory also where to place the file. RPMs are placed in privileged directories where you need sudo. This prevents tampering with the files by normal user processes or users. But this does not matter at all as long as you can execute scripts with bash even if the home directory is mounted nosuid noexec
(nonexecutable)
So how does one then go about getting the software into the rpm repo’s.
Obviously this is not something I can do, but, this to me is a vital bit of software, because I use it regulary.
I understand the security issues, but I make use of that software regularly.
Is there another electronics design suite that is supported under Fedora?
I am not sure an RPM actually makes this more secure in a meaningful way in this case.
If the publisher doesn’t provide signed packages, then the packager is just downloading them and placing them in rpm. The fact that the rpm is then signed only adds false security.
Arguably, getting an official image directly from the publisher is the best option in this case. The installer copies the application to /opt
and then creates a desktop file in /usr/share/applications
.
Since this is proprietary software, Fedora would need permission to repackage and distribute it. On top of that, it seems unlikely it would end up in the repos given Fedora’s policies.
This is really important to see.
The same goes for all signed uBlue images, including their signed Toolbox images that have some tweaks. These come from the unsigned Fedora OCI Images too.
oh, didnt see it is proprietary. Then you could still make a COPR and simply support it over time.
The advantage is
But using AppMan sounds like a way easier path