-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #220 appimage build script #226
base: develop
Are you sure you want to change the base?
Fix #220 appimage build script #226
Conversation
This is a draft as it needs further testing on different distros on my side. But you can help me testing and toy around with that first AppImage I made with this PR (two files are the same, one of those being GPG-signed, the other not). https://nuage.delalande.fr/s/TdDsYfsTMBxT9QC It won't overwrite your existing LIbreOsteo installation and data. It will use a new data (database and upload directory) within ~/.local/share/libreosteo to start playing :
|
- appstream - .desktop - icon suitable for freedesktop standard
Builds an executable standalone archive for current working copy. For now, this has to be triggered manually, but we may in near future want to : - trigger a build + upload on any commit on develop - trigger a build + upload for tagged releases Fix libreosteo#220
On subsequent runs, do not start anything but rather open web browser on LO URL. Ref libreosteo#220
a2e2625
to
c8db26e
Compare
@jbgury would it be possible to make the PR tested against travis, as I am trying stuff on travis ? (or maybe allow me to push to unprotected branches on libreosteo/Libreosteo repo ?) |
8078de7
to
023fcc6
Compare
@jbgury j'ai l'erreur suivante pour les tests fonctionnels :
Je ne vois pas trop ce que j'ai changé qui puisse casser ça. Une idée ? |
da53316
to
028d4ca
Compare
d3aa454
to
929f342
Compare
929f342
to
b5dddf6
Compare
Tu n'as plus le problème visiblement |
Oui, je ne sais pas trop si ça tient à quelque-chose que tu aurais fait ou au fait que moi j'ai configuré la CI sur mon fork. En tout cas c'est OK pour tester. |
Fix #220
That is a first step, that allow building AppImages locally.
If that looks good, I'd suggest that we build and upload (maybe using GH workflows ?) AppImage automatically
… And we should definitely start building AppImages for releases, but maybe manually, to allow further control and testing… and cryptographic signature (GPG).