AppImage/it

Che cos'è una AppImage?


AppImage è un "pacchetto binario universale" destinato a distribuire un'applicazione a qualsiasi distribuzione Linux. Maggiori informazioni al riguardo su Appimage homepage e Wikipedia.

Per eseguirlo, renderlo prima eseguibile, quindi digitare il percorso relativo o completo.

Per altri tipi di installazione vedere Download.

AppImages di FreeCAD
Note importanti:
 * Lo sviluppo avviene quotidianamente e rapidamente, il link di aggiornamento di AppImage è un obiettivo mobile.
 * Il link alla versione di sviluppo indicato sopra dovrebbe essere aggiornato perché viene aggiornato tramite uno script.
 * Molti utenti del forum utilizzano la versione di sviluppo.
 * Può essere eseguito sullo stesso sistema in parallelo con un'altra versione di FreeCAD.
 * Gli utenti usano la versione dev per sfruttare le ultime funzionalità e correzioni di errori (poiché FreeCAD ha un lungo ciclo di rilascio). La usano anche per aiutare a testare e trovare i bug per stimolare lo sviluppo e il miglioramento di FreeCAD.

Avviso di cautela obbligatorio
Per la maggior parte la versione di sviluppo è stabile ma ovviamente è importante aggiungere un obbligatorio avviso di cautela utilizzarla a proprio rischio. Anche se la maggior parte delle persone che utilizzano backup e "salvano spesso" fanno abbastanza bene.

Aggiornamento automatico
AppImage ha un modo intelligente ed economico di aggiornamento. Calcola la differenza tra il nuovo AppImage e quello vecchio e scaricherà solo le modifiche tra le loro versioni. In teoria l'utente finisce per scaricare circa il 15% ogni volta invece di un AppImage completamente nuovo.

L'aggiornamento automatico viene eseguito tramite diversi metodi opzionali. Attualmente ci sono 4 metodi, 2 attraverso l'interfaccia grafica (GUI) e 2 attraverso l'interfaccia a riga di comando / terminale (CLI).

Aggiornamento sperimentale in-app
Thanks to the efforts of several key devs, there is an ongoing effort to integrate a feature that allows self-updating the AppImage within FreeCAD itself. Starting from FC 0.19.21514 there now exists an AppImage section found via. Please test this capability and report your experience to the forum discussion.

GUI method 1 (official)
This is the official AppImageUpdate GUI application.
 * 1) Download AppImageUpdate-x86_64.AppImage.
 * 2) Make it executable by right clicking on the file, going in to properties and "Run as an executable".
 * 3) Double click on the AppImage icon, a dialog box will appear and you'll be prompted to specify what AppImage you want to update.
 * 4) Specify the path to your existing AppImage.
 * 5) Once the AppImage is updated, press the button.

GUI method 2 (unofficial)
This is a sleeker 3rd-party unofficial version of AppImageUpdate named: AppImageUpdater. It is still in development (at the time of this wiki edit) but nevertheless, quite nice to use. Result: Follow the AppImageUpdater prompts
 * 1) Download AppImageUpdater-*-x86_64.AppImage
 * 2) Make it executable:
 * 3) Run it:
 * 4) Find your current FreeCAD AppImage and drag-drop it on to the AppImageUpdater

CLI method 1 (official)
Run the following instructions in your terminal

Notes:
 * The file names will be unique because of the version info is embedded in them. The above instructions are simplified for convenience.
 * Run to learn about functionality like,  and.
 * There is also an i386 version; see the AppImageUpdate release page.

Todo: share a script that can be added as an alias or |cron job.

CLI method 2 (unofficial)
Similarly to the Graphical methods having an official and unofficial approaches to downloading AppImages, the same applies to the command line. This is a sleeker 3rd-party command line option to download AppImages.

Result: Updates specified AppImage file if update exists
 * 1) Download appimageupdater-*-x86_64.AppImage
 * 2) Make it executable:
 * 3) Run it:

= Experimental =

Fixing AppImage zsync
It may happen that an AppImage won't update because it's target file changed in some way. Instead of downloading a whole new AppImage, it's possible to rewrite the zsync file that is used by the AppImage to download the delta. More info can be found at https://github.com/antony-jr/appimage-update-info-writer.

This section needs more details.

Downloading via Bittorrent
An experimental feature that the FreeCAD packaging team is exploring (thanks to the work of Antony-jr) is being able to download an appimage delta of FreeCAD via bittorrent. The repository issue is at https://github.com/FreeCAD/FreeCAD-Bundle/issues/49

= Developer Section =

the following sections are intended for developers

Unpacking AppImages
A very convenient aspect of FreeCAD is that a majority of it is built in Python, which doesn't need to be manually compiled like C++. Essentially, a Python file can be modified, and upon restarting FreeCAD those changes will be integrated into the application. A developer can quickly work on the latest FreeCAD release using this technique and an AppImage. Moreover, using an AppImage doesn't modify your system's environment in any way, that is, nothing is installed and no environmental variables are modified.

Modifying AppImages
An AppImage embeds a file system in it with everything that is required to run the application. In order to modify it, the file system needs to be extracted.

Now open the required Python source files in your preferred code editor, modify them, and save them. Then run the application.

Repackaging AppImages
If you've modified the code, and now want to re-package the AppImage with your latest changes, use the appimagetool-x86_64 tool on the extracted file system.

Personalized AppImages
Thanks to the work of, author of App Link and Assembly3 Workbench, it is possible to build custom AppImages using a set of scripts.

This makes it very convenient to release images for a specific branch of the source code for others to test. Although AppImages only work on Linux, realthunder's scripts make it possible to generate AppImages also on Windows and MacOS.

The repository for these scripts is at realthunder/FreeCADMakeImage. Please read the Readme.md for more details.

Related

 * Snap packages.
 * Flatpak packages.