Search Criteria
Package Details: topgrade 16.0.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/topgrade.git (read-only, click to copy) |
---|---|
Package Base: | topgrade |
Description: | Upgrade all the things |
Upstream URL: | https://topgrade-rs.github.io |
Licenses: | GPL-3.0-or-later |
Submitter: | darwish |
Maintainer: | yochananmarqos (s34m) |
Last Packager: | yochananmarqos |
Votes: | 65 |
Popularity: | 0.73 |
First Submitted: | 2018-06-10 09:51 (UTC) |
Last Updated: | 2024-12-13 03:00 (UTC) |
Dependencies (2)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 Next › Last »
yochananmarqos commented on 2022-10-31 18:34 (UTC)
@Bricklou: There's nothing wrong with the source() array. Upstream tagged 10.1.0 earlier, but they since pulled it.
Bricklou commented on 2022-10-31 18:33 (UTC) (edited on 2022-10-31 18:33 (UTC) by Bricklou)
Hey, the PKGBUILD is wrong !
First, the
source
field should be like this:source=("${pkgname}-${pkgver}.tar.gz::${url}/archive/refs/tags/v${pkgver}.tar.gz")
And the
pkgver
field is10.0.1
not10.1.0
!D3SOX commented on 2022-10-25 15:53 (UTC)
Please update the source to the latest release of https://github.com/topgrade-rs/topgrade
darwish commented on 2022-10-23 13:09 (UTC)
@dotto you are now a co-maintainer of the package
darwish commented on 2022-10-23 13:09 (UTC)
@dotto you are now a co-maintainer of the package
solnce commented on 2022-10-18 12:26 (UTC)
I have sent an email to the submitter and maintainer to ask for either an update or disowning the package.
s34m commented on 2022-10-17 21:21 (UTC)
Maintainer here, I released 9.1.0 now.
yochananmarqos commented on 2022-10-17 14:02 (UTC)
@TechXero: The new fork has no releases yet, there's nothing to be done here.
TechXero commented on 2022-10-17 09:03 (UTC)
PKGBUILD should be updated to reflect new fork as main dev has decided to abandon project...
Drew commented on 2022-09-08 21:47 (UTC)
All dependencies should be handled by the PKGBUILD. This is not OK:
You shouldn't have some requirement like "the user must first run command xyz before building." It needs to work on a clean installation of arch as long as all the dependencies have been installed via pacman. Otherwise you're just blocking people from automating system upgrades. Doesn't that defeat the purpose of this product?
Anyway, you should make sure this is building with the proper toolchain regardless. Something like this would be more reliable:
or put it in Cargo.toml
And you'll need to make sure it's available on the user's system. This works:
That doesn't work for people who satisfy the
rust
dependency with something other than rustup, but frankly there's no good reason to do that. Attempting to accommodate users who set up their system incorrectly is only introducing unnecessary complexity. I would make rustup itself a dependency rather than just rust.« First ‹ Previous 1 2 3 4 5 Next › Last »