Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Proposal: AUR package (openpets-bin) for Arch/CachyOS

Open
  • Is something wrong?
#232 13 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
arch-linux, electron, typescript
Domain
desktop, release

Research direction

The proposal asks whether an AUR package is welcome and raises naming, release version updates, and README or docs linking; it names no repository files or tests. First, check the maintainer’s response in this discussion for approval and preferences. Done would mean an agreed package name and maintenance approach, followed by a published AUR package and an approved documentation link.

Written by the indexing model from the issue text.

Description

Hi alvinunreal,

I've loved openpets since I first came across it a few months ago. It's become a must-have on all my Linux machines! I filed #119/PR #120 a while back (merged into v3.4.0), and more recently opened #221-223 with fixes in #224-226 for a few bugs I ran into testing v4.0.0. I've been running OpenPets from source pretty heavily on a couple of CachyOS machines, and was thinking about putting together an AUR package so Arch/CachyOS users could install your app with a simple paru -S openpets-bin instead of manually grabbing the AppImage. Another benefit of an AUR package is the app would be updated when a user updates their system with paru -Syu.

I'm wondering if you are okay with an AUR package existing at all. Some projects would rather stick to AppImage/Flatpak-only distribution, or want to publish under an official name themselves...

If you're ok with me maintaining an AUR package:

  • Any preference on naming? openpets-bin is the usual AUR convention for a package that just wraps a binary/AppImage release, but wanted to check you don't already have one planned or a name you'd prefer.
  • How would you want version bumps handled — should I just watch your repo for new GitHub releases and update the package myself, or would some other signal work better?
  • Would you link it from the README/docs once it's up? That lends the package a lot of credibility if you approve.

Let me know what you think. -Pinoybear

Dominant language
TypeScript
Stars
1.3k
Forks
125
Avg merge
5h 8m
Merged PRs (30d)
35

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenPetsHQ/openpets

All issues in OpenPetsHQ/openpets

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.