Package Details: starship-bin 0.25.0-1

Git Clone URL: (read-only)
Package Base: starship-bin
Description: The cross-shell prompt for astronauts
Upstream URL:
Licenses: ISC
Conflicts: starship
Provides: starship
Submitter: chipbuster
Maintainer: chipbuster
Last Packager: chipbuster
Votes: 5
Popularity: 2.526038
First Submitted: 2019-08-23 17:20
Last Updated: 2019-10-16 14:31

Latest Comments

1 2 Next › Last »

chipbuster commented on 2019-10-16 16:16

Got it, that makes total sense. Thanks a bunch.

toyarchery commented on 2019-10-16 14:40

Problem with upstream package naming is that there's no version difference, so AUR helpers might assume the package was already made without checking the checksum

This way each package gets a unique name, which also makes it easier to manage and more consistent with other packages

lightning1141 commented on 2019-10-16 14:38

if you don't rename the package, checksum will failed when you upgrade it, cause most aur tools will use the cached package.

Warning: The downloaded source filename must be unique because the SRCDEST directory can be the same for all packages. For instance, using the version number of the project as a filename potentially conflicts with other projects with the same version number. In this case, the alternative unique filename to be used is provided with the syntax source=('unique_package_name::file_uri'); e.g. source=("$pkgname-$pkgver.tar.gz::$pkgver.tar.gz").

chipbuster commented on 2019-10-16 14:31

@lightning1141 Happily done for the 0.25.0 version bump.

I'm a little new to making packages--do you have a link explaining the syntax or why this should be done? I didn't find anything about it on the wiki page about creating packages.

lightning1141 commented on 2019-10-16 14:17

please rename downloaded package like this:


pepper_chico commented on 2019-10-09 23:23

Not passing validity check again.

pepper_chico commented on 2019-10-05 20:52

@chipbuster, it's fine now, thanks.

chipbuster commented on 2019-10-05 19:49

Sorry all, looks like the change to the upstream packaging system broke the scripts I use to update the PKGBUILD. I probably should have realized this, but for some reason I didn't think about it.

I think I've fixed the issue now, let me know if anything else is giving you trouble.

pepper_chico commented on 2019-10-05 17:27

It's not passing validity check.

toyarchery commented on 2019-10-05 11:03

Remove the 'cd x86_64-unknown-linux-gnu' line, it's no longer needed, and change version to 0.20.2 while you're at it (it has just released)