Search Criteria
Package Details: devbox 0.13.6-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/devbox.git (read-only, click to copy) |
---|---|
Package Base: | devbox |
Description: | A cli tool to easily create isolated shells and containers |
Upstream URL: | https://github.com/jetpack-io/devbox |
Licenses: | Apache-2.0 |
Submitter: | alerque |
Maintainer: | alerque |
Last Packager: | alerque |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2022-09-13 14:13 (UTC) |
Last Updated: | 2024-10-29 11:15 (UTC) |
Dependencies (3)
- nix (nix-gitAUR)
- go (go-gitAUR, gcc-go-gitAUR, go-sylixosAUR, gcc-go-snapshotAUR, gcc-go) (make)
- docker (rancher-desktop-gitAUR, podman-docker-gitAUR, docker-cli-binAUR, rancher-desktopAUR, docker-gitAUR, podman-docker) (optional) – for container support
Latest Comments
barraponto commented on 2024-11-19 17:05 (UTC)
@alerque yes, it's bad. AUR packages have a release version, though. Can't we use that?
alerque commented on 2024-11-01 12:26 (UTC)
@prettyvanilla @barraponto Somebody please open an upstream issue to ask them to stop re-tagging releases after posting them. This is at least the third time it's happened since I've been packaging it and it takes a lot of effort to fix (we have to verify the changes because it breaks our trust-on-first-use model, I have to manually change source names to clear build caches, etc.). If releases are so broken they can yank the tag, but the next tag should be a new version not a repeat of an already posted tag.
prettyvanilla commented on 2024-09-30 09:54 (UTC)
It seems like the latest tag was updated to a newer commit as the checksums don't match at the moment:
The sha256sum of the compressed tar is now
ce42de27b7dcf5ba64bcdf4fb4f102cfe4dc08ad90126b389b4ed9bbf4816a54
on my end.