{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

Ultimately this comes down to changing the versioning string for "Hometown version 1.0.8, synchronized with Mastodon 3.5.5" from

1.0.8+3.5.5

to

3.5.5+hometown-1.0.8

I still cringe a little to look at it but I understand that it'll help other projects and I really want as much 3rd party Hometown support as possible.

As usual: please don't ask why I have decided to do it this way or propose alternatives until you have read the Github thread which contains the rationale.

6
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Mark Sample

@darius Before I read the Github thread which contains the rationale, please let me ask why you've done it this way, because I have some alternatives to propose.

1
2y
Conny Duck

@darius that makes total sense, thank you!

1
2y
Travis Castillo

@darius i always run into this problem forking libraries and trying to publish feature branches.

0
2y
Jake

@darius It’s so cool you and the author of that script working this out. Thank you!

0
2y
Shadowfacts :ivoted1:‍:ivoted2:
@darius i shall update my version parsing logic to be version dependent 🫡
1
2y
Till Krüss

@darius makes sense. I just set up an instance for my hometown at nelson.social :owi:

0
2y
Replies