~mil

http://milesalan.com

I'm Miles, also see: http://milesalan.com

My nick is mla on IRC.

~mil/sxmo-devel

Last active 48 minutes ago

~mil/mepo-devel

Last active 2 days ago

~mil/sxmo-announce

Last active 3 days ago

~mil/sxmo-user

Last active 16 days ago

~mil/framebufferphone-devel

Last active 3 months ago

~mil/foo

Last active 2 years ago
View more

Recent activity

Re: [PATCH mepo] unpin zig patch number 2 days ago

From Miles Alan to ~mil/mepo-devel

On Wed, Feb 1, 2023, at 9:42 AM, laalsaas wrote:
> A patch release shouldn't have any breaking changes. However, pinning
> the patch means reducing the tolerance for different zig versions in
> software repositorys to zero.
> ---
> NixOS only has zig 0.10.1, however mepo 1.1.1 still pins zig 0.10.0,
> while mepo 1.1.2 isn't released yet.
>
>  src/main.zig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/main.zig b/src/main.zig
> index 513038e..33c78f2 100644
> --- a/src/main.zig

Mepo - February 2023 update: 1.1.2 Released to build against zig 0.10.1 2 days ago

From Miles Alan to ~mil/mepo-devel

Hi all,

A minor tag for mepo, 1.1.2, has been released.
This release updates the codebase to build against zig 0.10.1.

Cheers,
Miles

Announcing Mobroute - Minimal FOSS Public Transportation Router proof of concept 7 days ago

From Miles Alan to ~mil/mepo-devel

Hi all,

Today I'm announcing a new companion project to Mepo focused on
providing public transportation routing directions based on the
Mobility Database (https://database.mobilitydata.org/). The project is
named Mobroute and allows you to route between geocoordinates based on
GTFS data automatically pulled down upon use. The core of the routing
implementation is based on Dijkstra's algorithm and Mobroute provides
a nice and simple end-user CLI for usage. The project repository is
available at http://git.sr.ht/~mil/mobroute and I'll be using the Mepo
mailing list and bug tracker for now to also manage Mobroute development.
As a disclaimer, the project is currently in active development and
currently more of a proof-of-concept then something usable atleast at
the moment; so don't expect much to work yet..

Re: Missing Version bump in 1.1.1 a month ago

From Miles Alan to ~mil/mepo-devel

On Mon, Nov 28, 2022, at 12:45 PM, laalsaas wrote:
> I think you forgot to bump the version for the new release, at least
> `mepo -v` still outputs 1.1 as version.

Thanks for mentioning, since there were no end-user API / mepolang
updates for 1.1.1 from 1.1, I consider this a bug for 1.1 but I don't
plan to publish 1.1.2 revision just for this. Its noted that I'll make
sure to bump the version number for minor revisions for future releases.

Mepo - November update: 1.1.1 Released to build against zig 0.10.0 2 months ago

From Miles Alan to ~mil/mepo-devel

Hi all,

A minor tag for mepo 1.1.1 has been released in order to update the
codebase to use zig 0.10.0.  Release notes for this tag are below:

---------------------------------------------------------------------------

# 1.1.1 Release Notes

This is a minor release in order to update the codebase to build against
zig 0.10.0.  The mepo 1.1 tag was built against zig 0.9.1.  This release
tag, 1.1.1, builds against zig 0.10.0.

In addition to the build update to update to zig 0.10.0, the following

Re: [PATCH mepo] fix user_pin_updater on all locales 2 months ago

From Miles Alan to ~mil/mepo-devel

On Fri, Oct 28, 2022, at 11:44 PM, laalsaas wrote:
> The script mepo_ui_menu_user_pin_updater is using geoclue per default.
> However, the where-am-i binary outputs the coordinates in a number
> format which is locale-specific. i.e. if you've set
> LC_NUMERIC="de_DE.UTF-8" , where-am-i will use the comma as the decimal
> seperator instead of the point. This will lead to the following mepolang
> statement produced by the script:
>
>> pin_add 6 0 51,028178 13,710861 user_location;
>
> Mepo can't deal with this and will silently ignore it. The fix is to set
> the LC_NUMERIC variable to en_US for calling where-am-i.
> ---
>  scripts/mepo_ui_menu_user_pin_updater.sh | 2 +-

Re: [PATCH] make userpin updater less verbose 2 months ago

From Miles Alan to ~mil/mepo-devel

On Wed, Oct 26, 2022, at 5:38 PM, laalsaas wrote:
> ---
>  scripts/mepo_ui_menu_user_pin_updater.sh | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/scripts/mepo_ui_menu_user_pin_updater.sh 
> b/scripts/mepo_ui_menu_user_pin_updater.sh
> index 8881ca4..a6b13ab 100755
> --- a/scripts/mepo_ui_menu_user_pin_updater.sh
> +++ b/scripts/mepo_ui_menu_user_pin_updater.sh
> @@ -37,13 +37,13 @@ coordsviageoclue() {
>  }
> 
>  supportsgeoclue() {

Mepo - November update: 1.1 Released 3 months ago

From Miles Alan to ~mil/mepo-devel

Hi all,

Welcome to the November update for Mepo covering the 1.1 release. You
can follow Mepo's development at http://sr.ht/~mil/mepo and do note
that release notes are also mirrored in the git annotated tags for
each release.

---------------------------------------------------------------------------
Contents:

1.1 Release Notes:
- Addition of new pin_transfer & pin_delete commands
- Top UI buttons & bind_button improvements
- Menuing switched to use zenity for all environments; dmenu/bemenu dep removed

Re: [PATCH mepo] Make Geoclue timeout configurable 3 months ago

From Miles Alan to ~mil/mepo-devel

On Mon, Oct 17, 2022, at 1:58 AM, Nguyễn Gia Phong wrote:
> Stop executing where-am-i in the background since there isn't
> seem to be a reason to do so.
> ---
>  scripts/mepo_ui_menu_user_pin_updater.sh | 15 ++++++---------
>  1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/scripts/mepo_ui_menu_user_pin_updater.sh 
> b/scripts/mepo_ui_menu_user_pin_updater.sh
> index 09ce16b16c1d..24fed64e3fe2 100755
> --- a/scripts/mepo_ui_menu_user_pin_updater.sh
> +++ b/scripts/mepo_ui_menu_user_pin_updater.sh
> @@ -13,6 +13,7 @@ DOC='
>  [ -z "$MEPO_USERPIN_ENABLED" ] && MEPO_USERPIN_ENABLED="1"

Re: Non Posix-Compliance found 3 months ago

From Miles Alan to ~mil/mepo-devel

On Sat, Oct 15, 2022, at 12:12 PM, Hendursaga wrote:
>> However, I think you get the idea that POSIX compliance is important, especially with the fact in mind that postmarketOS, uses just busybox coreutils.
>
> I too would prefer POSIX compliance. Grepping the codebase, I see a few 
> references to ignoring shellcheck[1] warnings, but no Git hooks or 
> anything, so I'm supposing it's up to the devs to use shellcheck on 
> their own?? I know it catches some POSIX compliance issues but misses 
> others[2], but it could be a step in the right direction!
>
> ~ Hendursaga
>
> [1] https://www.shellcheck.net/
> [2] https://github.com/koalaman/shellcheck/issues/2125