Skip to content

Signed tags or releases #67

@aminvakil

Description

@aminvakil

First of all, I want to thank you for this brilliant project, it works well for me by downloading artifacts.

Although I'd prefer packaging it in a system package, and I'm going to setup slipstream-git package on AUR (Arch Linux User Repository) where anyone can upload their PKGBUILD which can be used by others.

Something like this: https://gitlab.archlinux.org/archlinux/packaging/packages/dust/-/blob/main/PKGBUILD?ref_type=heads

Anyway it's fine to package it in AUR with -git extension which shows it uses latest commit of main branch and will produce a new package whenever a new commit has been pushed and you build the package again, it would be nicer to have a tag, preferably signed, so that everyone can track a new version easily.

I do not care for semver, calver, or whatever versioning which you prefer, but that's a necessity for a package to be included in Arch official repositories where I would want it to be, although I'm not a package maintainer in Arch Linux myself, but I think I can convince a PM to adopt my package from AUR if there is a tag from this repository.

TLDR; What do you think about issuing tags (preferably signed)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions