Date: prev next · Thread: first prev next last
2022 Archives by date, by thread · List index


Hi all,

Sorry for the (probably stupid and already addressed several times) questions this mail will surely contain.

I'm trying to automate the building of AppImage for LibreOffice, starting from the good work of Antonio Faccioli [1]. For the sake of clarity, those AppImage builds are basically a repackage of the .deb contents from TDF-released packages.

I have some questions:
* Are x86-based (32bit) builds definitely abandoned? I don't see any x86 builds in the dev-builds.lo.org site nor in download.df.org site; * Is there any other smarter way to know the last available .deb build, both for stable releases and for daily builds, than parsing those pages? * As a side note, do you have a tool of choice for triggering such builds? What is the workflow (in a few words) there? I'm giving Rundeck [2] a spin for this.

Cheers,

[1]: https://github.com/antoniofaccioli/libreoffice-appimage/blob/master/make_libreoffice_appimage
[2]: https://www.rundeck.com/open-source
--
Emiliano Vavassori
syntaxerrormmm@libreoffice.org

--
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/website/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.