taivlam / aur-mpr-packages

List of AUR and MPR packages I maintain

My AUR and MPR packages

My PKGBUILD shell scripts for the AUR and MPR packages that I maintain

Repology list (base package names; will use widgets later)

AUR

• mudita-center-appimage
• mouse-configurator

MPR

• bitwarden-bin
• electronmail-bin
• ente-auth-bin (needs fixing)
• freetube-bin
• organicmaps (needs fixing)

Planned

• ente-desktop-bin (WIP)
• ferdium-bin (WIP)
• glow (uncertain)
  • Also glow-bin (uncertain)
• playdate-mirror (TBD)
• playdate-sdk (TBD)
• vnote (WIP)
  • Also vnote-bin (WIP, waiting until CVE in version 3.17 is patched)
  • See: vnotex/vnote#2446

Packaging checklist

Creating/Adopting new package

• Declare Maintainer
  • Denote past Maintainers as Contributors (if needed)
• Change your displayed User Name and E-mail Address for Git repo!

  $ git config user.name "First-name Last-name"
  $ git config user.email "[email protected]"
  

  • Otherwise, you cannot do this later!

Updating package

• Change:
  • pkgver
  • pkgrel (if needed)
  • Checksums
    • Most common & cryptographically sound checksums (as of Feb 2024)
      • SHA256
      • SHA512
      • BLAKE2 (i.e., the b2sum command in GNU Core Utilities)
    • Download the specified archive from the source (e.g. GitHub, GitLab, direct software source page, & so on)
• Update .SRCINFO package metadata file with:

  $ makepkg --printsrcinfo > .SRCINFO
  

• Lastly, add the files, make a commit, and push the changes:

  $ git add .
  $ git commit -m "Add message here"
  $ git commit --amend    # Write a longer message here, if needed
  $ git push
  

Sources from the ArchWiki

• AUR
  • AUR Submission Guidelines
• .SRCINFO

License

The license for the PKGBUILD scripts I author are under the GNU General Public License Version 3 (GNU GPLv3).

aur-mpr-packages's Issues

electron-mail

continuation from here:
vladimiry/ElectronMail#684

1. lol... i actually never used it.
2. Don't worry about that, it happens some times. About the comment notifications, i'm not 100% sure, but i think that's broken for a while now.
3. Yea ok.
4. Upstream is the developer, vladimiry, here. He already builds debs and also publish their sha256, that's why it's preferable to use sha256. The AUR package actually builds a arch package. The mpr package, just unpacks and then repacks the deb that vladimiry makes... It's not completely useless, It's more convinient then downloading the deb your self manually. One of the changes that i made, is that the PKGBUILD just downloads the package and doesn't unpacks and then repacks it.
5. here i am
6. an email address would be preferable. Use a dedicated one for this.

The new PKGBUILD

PKGBUILD.txt