Search Criteria
Package Details: stardust-xr-telescope 0.1.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/stardust-xr-telescope.git (read-only, click to copy) |
---|---|
Package Base: | stardust-xr-telescope |
Description: | See the stars! Simple Stardust XR overlay setup. |
Upstream URL: | https://github.com/StardustXR/telescope |
Licenses: | MIT |
Submitter: | technobaboo |
Maintainer: | technobaboo |
Last Packager: | technobaboo |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2024-10-26 13:05 (UTC) |
Last Updated: | 2024-11-16 18:04 (UTC) |
Dependencies (8)
- bash (bash-devel-static-gitAUR, bash-devel-gitAUR, busybox-coreutilsAUR, bash-gitAUR)
- stardust-xr-black-holeAUR
- stardust-xr-flatlandAUR
- stardust-xr-gravityAUR
- stardust-xr-protostarAUR
- stardust-xr-serverAUR
- xwayland-satelliteAUR (xwayland-satellite-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
Latest Comments
Nebulosa commented on 2024-11-16 20:12 (UTC) (edited on 2024-11-16 20:12 (UTC) by Nebulosa)
As I understand you question, yes, you should make release on a github and edit some lines in PKGBUILD after. I can help with edits after making a release.
technobaboo commented on 2024-11-16 17:22 (UTC)
oh right, generally releases in stardust are rebased from the dev branch to the main branch... is it important to use github releases and pull from there?
Nebulosa commented on 2024-11-16 13:09 (UTC) (edited on 2024-11-16 13:10 (UTC) by Nebulosa)
You should make an first release e.g.
0.0.1
for using package name without-git
.If you not plans make a release, you should make an another package
stardust-xr-telescope-git
. I can help with writing PKGBUILD for you if you wish.And you should do this for all of your
stardust-xr-*
packages.