https://github.com/fwdekker/aur-mommy

aur package for mommy~ ❤️
https://github.com/fwdekker/aur-mommy

archlinux aur makepkg mommy pkgbuild

Last synced: 2 days ago
JSON representation

aur package for mommy~ ❤️

• Host: GitHub
• URL: https://github.com/fwdekker/aur-mommy
• Owner: FWDekker
• Created: 2023-03-03T16:22:06.000Z (almost 2 years ago)
• Default Branch: master
• Last Pushed: 2024-09-29T11:04:25.000Z (5 months ago)
• Last Synced: 2025-02-07T06:08:51.091Z (7 days ago)
• Topics: archlinux, aur, makepkg, mommy, pkgbuild
• Language: Shell
• Homepage: https://github.com/FWDekker/mommy
• Size: 27.3 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# aur-mommy 🔺

arch linux build files for [mommy](https://github.com/FWDekker/mommy), synchronised with the

[arch user repository](https://aur.archlinux.org/packages/mommy) (aur)~

see [mommy](https://github.com/FWDekker/mommy) for installation instructions~

## ⚗️ development

### 🚨 warnings

* **never force push**

* **commits pushed to `master` are irreversibly synced with [aur](https://aur.archlinux.org/packages/mommy)**

* **`dev` must never be behind `master`**

* **be careful when editing `.aurignore`**  

  changes to this file should never affect commits that are already in the aur.

  careless changes may cause deployment failures

### 🫒 branch management

#### 🤔 what do the branches contain?

* `aur-mommy#master` contains the released build script for building the

  [latest release of `mommy`](https://github.com/FWDekker/mommy/releases/latest), and is mirrored to the

  [aur repository](https://aur.archlinux.org/packages/mommy)

* `aur-mommy#dev` contains the unreleased build script for building the latest commit to `mommy#main`, and is not

  mirrored to the aur repository

if you **locally** want to point the build script to a different commit, run `./update.sh ` to make it build

`mommy#`~

#### 🔍 where should i push my changes?

> ⚠️ below, we will be comparing branches across different repos!

>

> `mommy#dev` is not `aur-mommy#dev`!

note that pushing to `aur-mommy#master` will also [immediately sync](#-release) to the aur.

therefore, most changes should instead go to `aur-mommy#dev`.

these changes will be merged into `aur-mommy#master` automatically when a new [mommy](https://github.com/FWDekker/mommy)

release is created~

if all changes in a commit are to files listed in

[`.aurignore`](https://github.com/FWDekker/aur-mommy/blob/master/.aurignore) (of that branch), no changes are pushed to

the aur, so those commits are really quite safe.

but keep in mind, **`aur-mommy#dev` must never be behind `aur-mommy#master`**~

for all other cases, consider whether you want to push only to `aur-mommy#dev`, or to both `aur-mommy#dev` _and_

`aur-mommy#master`.

this choice should be based on compatibility of the change with

[the version that branch points to](#-what-do-the-branches-contain)~

### 📯 release

the release process is fully automatic.

no human intervention required.

below is a brief summary of how it works~

when a new [mommy](https://github.com/FWDekker/mommy) release is created,

[its cd action](https://github.com/FWDekker/mommy/blob/main/.github/workflows/cd.yml)

1. merges `aur-mommy#dev` into `aur-mommy#master`

2. runs [`update.sh`](https://github.com/FWDekker/aur-mommy/blob/master/update.sh) on `aur-mommy#master` to bump version

   info,

3. and commits and pushes these changes to `aur-mommy#master`~

this then invokes [`aur-mommy`'s cd action](https://github.com/FWDekker/aur-mommy/blob/dev/.github/workflows/cd.yml),

which

1. removes files listed in `.aurignore` the history using

   [git filter-repo](https://github.com/newren/git-filter-repo/), so aur doesn't complain about nested directories

   and unwanted files, and

2. pushes the filtered repo to [aur](https://aur.archlinux.org/packages/mommy)~