---
src/pages/installguide.md | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/src/pages/installguide.md b/src/pages/installguide.md
index c3b2c07..5defaf8 100644
--- a/src/pages/installguide.md+++ b/src/pages/installguide.md
@@ -31,7 +31,23 @@ in the launcher for mepo based on the `.desktop` file.
---
-## Flatpak+## Compile from source++Alpine Linux maintainers are waiting for zig to release 1.0 before zig is merged into stable.+As such, mepo is not available in the postmarketOS/Alpine stable repositories.+You can use flatpak to install mepo.+If you don't want to install flatpak, here is how you can compile mepo from source on Alpine/postmarketOS stable:++1. Install the `makedepends` and `depends` packages from the [APKBUILD]( https://git.alpinelinux.org/aports/tree/testing/mepo?h=master).+2. Download and unpack `zig-linux-<your-arch>-<version>.tar.xz` from the [ziglang website](https://ziglang.org/download/). Once unpacked, the `zig` binary in the `zig-linux-<your-arch>-<version>` folder is your zig compiler.+3. Get and build the mepo source: `git clone https://git.sr.ht/~mil/mepo && cd mepo && ../zig-linux-<your-arch>-<version>/zig build`.+4. Install mepo via: `doas cp zig-out/* /usr/local`.++Mepo should now appear in your applications menu (phosh, Sxmo, etc.).++---++## flatpakMepo is available [as a flatpak on
flathub](https://flathub.org/apps/details/com.milesalan.mepo).
--
2.40.1
On 2023-05-24 at 22:29-07:00, Anjandev Momi wrote:
> +3. Get and build the mepo source: `git clone https://git.sr.ht/~mil/mepo && cd mepo && ../zig-linux-<your-arch>-<version>/zig build`.
Assuming this guide is intended for end users, I think releases
should be recommended instead: https://git.sr.ht/~mil/mepo/refs
I don't speak for the maintainer, but the file is currently wrapped
at around column 72, so it also might be a good idea to keep it
that way. Personally I'd at least expect a code block instead of
multiple commands &&-chained together for better readability.
On 2023-05-24 at 22:29-07:00, Anjandev Momi wrote:
> +4. Install mepo via: `doas cp zig-out/* /usr/local`.
I am not sure global installation without a package manager
is good practice. I suggest following XDG recommendations
for user files, i.e. `zig build --prefix ~/.local install`
On 2023-05-24 at 22:29-07:00, Anjandev Momi wrote:
> -## Flatpak> [snip]> +## flatpak
I believe this was an accident.
On Thu, May 25, 2023, at 2:19 AM, Nguyễn Gia Phong wrote:
> On 2023-05-24 at 22:29-07:00, Anjandev Momi wrote:>> +3. Get and build the mepo source: `git clone https://git.sr.ht/~mil/mepo && cd mepo && ../zig-linux-<your-arch>-<version>/zig build`.>> Assuming this guide is intended for end users, I think releases> should be recommended instead: https://git.sr.ht/~mil/mepo/refs>> I don't speak for the maintainer, but the file is currently wrapped> at around column 72, so it also might be a good idea to keep it> that way. Personally I'd at least expect a code block instead of> multiple commands &&-chained together for better readability.>> On 2023-05-24 at 22:29-07:00, Anjandev Momi wrote:>> +4. Install mepo via: `doas cp zig-out/* /usr/local`.>> I am not sure global installation without a package manager> is good practice. I suggest following XDG recommendations> for user files, i.e. `zig build --prefix ~/.local install`>> On 2023-05-24 at 22:29-07:00, Anjandev Momi wrote:>> -## Flatpak>> [snip]>> +## flatpak>> I believe this was an accident.
Generally for end-users Flatpak is the recommend install method if
packaging is unsupported.
We also do have the development guide which can assist for compiling
from source instructions separately at:
http://mepo.milesalan.com/developguide.html