owasp-threat-dragon-desktop
owasp-threat-dragon-desktop copied to clipboard
mike-goodwin
Question: difference between AMD64 and X86 64 bit Debian packages
Hi,
I was wondering if you could document the difference between AMD64 and X86 64 bit Debian packages.
At https://github.com/mike-goodwin/owasp-threat-dragon-desktop/releases I can only see
Debian package for AMD64 : threatdragon_1.2.0_amd64.deb
Debian package for X86 64 bit : threatdragon_1.2.0_x86_64.deb
They also have different sizes, but just looking at this I don't know what the difference is and which I should use.
Hello @MichaelGissingNC - it depends on the processor type in your Linux machine. If in doubt do you want to try the Linux AppImage? OWASP-Threat-Dragon-1.2.0.AppImage
@jgadsden What's the difference? Debian only knows amd64 and all I know is that x86_64 usually is the same ISA as amd64.
Hello @MichaelGissingNC - as far as I know the two packages are subtly different according to the type of hardware platform. Can you run lscpu and see what processor type you have?
For example on my machine:
threat-dragon-desktop$ lscpu
Architecture: x86_64
...
I can modify the release notes to make this more clear
@jgadsden It's x86_64 as well, but in Debian terminology this is amd64 for packages. In all my encounters with architectures in recent years, these two are synonyms.
Ah, I have had different experiences and need to use the correct package on my Trisquel box. I have updated the release notes, does this provide enough clarity in these notes? Happy to apply any changes that you want to see
OK, I had a closer look at the packages, they also differ in installed files, installation target and dependencies.
Can you point me to the build scripts for the packages? Maybe I can figure out what the different packages are supposed to do.
Sure, there are two files that determine this: electron-builder.json and installer-lin.js. If you see any tidy-ups then feel free to raise a pull-request.
Note that Mike's repos have been migrated to https://github.com/OWASP/threat-dragon-desktop and so any pull-request should be done in that repo