#13 Ensure user can always publish posts

For now I think I’ll package the CLI app in the same Debian package as this app, to keep everything in one repository.

Though it would be cleaner to package the CLI seperately (and while you’re at it, your brand fonts) and declare them as dependencies. This would also require setting up your own package repository, which is a common thing for many projects anyways just as a way to distribute updates.

I’ve been going through these tasks faster then I originally thought (given how much I struggled last time) so let me know if you want me to help get you started with that approach.

Yeah, I’d like it to be set up the right way, and would definitely appreciate your advice on the best way to do it. I have started getting a PPA going for the CLI before here, but wasn’t sure if I was doing it the right way

O.K., I just failed to pull the CLI into this same package anyways.

I’ll contribute debian packaging to https://github.com/writeas/writeas-cli, though I haven’t done it for go packages before. So I wouldn’t know if I’m doing that right either.

I’m not all that experienced with Debian packaging, bascially I just know how to package anything with a Meson or Make build systems.

Packaging Go code is new to me, and ideally the font “Lora” should also be installed alongside writeas-gtk. I have some knowledge of what is involved in packaging fonts, but not a working knowledge of how to do so.

I’ve given a go at packaging your CLI for Debian, and if that fails for you I’ve got some other ideas to try out with you. But you may go further by finding sysadmin who knows these tools better than me.

Awesome, thanks for trying that out -- I’ll take a look.

It’d be great to get any help you could offer on packaging up Lora, since that’s such a key font for Write.as.