The CI makes a draft release. I hate automated releases and it lets me write the changelog in before publishing.
Search Criteria
Package Details: paru 2.0.4-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/paru.git (read-only, click to copy) |
|---|---|
| Package Base: | paru |
| Description: | Feature packed AUR helper |
| Upstream URL: | https://github.com/morganamilo/paru |
| Keywords: | AUR helper pacman rust wrapper yay |
| Licenses: | GPL-3.0-or-later |
| Submitter: | Morganamilo |
| Maintainer: | Morganamilo |
| Last Packager: | Morganamilo |
| Votes: | 982 |
| Popularity: | 19.64 |
| First Submitted: | 2020-10-19 00:43 (UTC) |
| Last Updated: | 2024-09-20 18:50 (UTC) |
Dependencies (6)
- git (git-gitAUR, git-glAUR)
- libalpm.so (pacman)
- pacman (pacman-gitAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- bat (bat-cat-gitAUR) (optional) – colored pkgbuild printing
- devtools (devtools32-gitAUR, devtools-gitAUR, devtools-doasAUR) (optional) – build in chroot and downloading pkgbuilds
Required by (31)
- aconfmgr-git (optional)
- arch-os-manager (optional)
- arch-update (optional)
- arch-update-git (optional)
- dec-bin
- dec-git
- fe
- fuzzy-pkg-finder (optional)
- fzpac (optional)
- fzpac-git (optional)
- iwant (optional)
- iwant-bin (optional)
- lsparu
- meta-package-manager (optional)
- meta-package-manager-git (optional)
- octopi (optional)
- packageprovides (optional)
- pacrs (optional)
- pacup-arch-git (optional)
- pacupdate-git
- Show 11 more...
Sources (1)
Morganamilo commented on 2021-06-25 17:59 (UTC)
alerque commented on 2021-06-25 17:52 (UTC)
It does make me wonder what happened to this CI run that claims to have been successful. I don't see the expected results...
alerque commented on 2021-06-25 17:41 (UTC)
@Det True this PKGBUILD uses the git archive source link anyway, but for projects that actually use releases as opposed to just tagging, the extra automated stuff can be important. If it goes wrong you make want to fix it and try again, in which case the hash would change. Packaging any platform before all platform builds are finished would be a mistake.
Det commented on 2021-06-25 17:37 (UTC) (edited on 2021-06-25 17:39 (UTC) by Det)
+ but basically the tarball for the non-release tagged one is the same (even when released), it only has some extra testing parts that don't even affect the build.
alerque commented on 2021-06-25 17:36 (UTC) (edited on 2021-06-25 17:38 (UTC) by alerque)
@Det The difference is pretty obvious in the GitHub interface if you look at the releases page. You can see what are just tags and what tags have been turned into releases with changelogs and attached assets at a glance. Another way to tell is using the latest keyword link.
Det commented on 2021-06-25 17:02 (UTC)
Idek what that means. :heart:
Morganamilo commented on 2021-06-25 17:00 (UTC)
You can consider the tag as "going gold" in video game terms.
Det commented on 2021-06-25 16:59 (UTC)
Ah. Slightly confusing.
This doesn't even use the binaries. :shrug:
Morganamilo commented on 2021-06-25 16:54 (UTC)
Tags are just part of version control. Weather it's released or not is separate. Especially since the tag triggers the CI to do stuff to prepare for the release such as binary builds.
Det commented on 2021-06-25 16:48 (UTC)
You tagged 1.7.3 tho, and it's obtainable from https://github.com/Morganamilo/paru/archive/refs/tags/v1.7.3.tar.gz?
Pinned Comments
haxie commented on 2023-05-26 17:45 (UTC)
you're better off contacting her via the github, this comments section is 90% "it's out of date" from people who didn't scroll down before posting