Package Details: lib32-rust-libs-git 1:1.96.0.r1.g0312931-1

Git Clone URL: https://aur.archlinux.org/rust-git.git (read-only, click to copy)
Package Base: rust-git
Description: 32-bit target and libraries for Rust (GIT VERSION)
Upstream URL: https://www.rust-lang.org/
Keywords: cargo rust
Licenses: Apache-2.0 OR MIT
Conflicts: lib32-rust, lib32-rust-libs
Provides: lib32-rust, lib32-rust-libs
Replaces: lib32-rust
Submitter: mrshpot
Maintainer: kaolinite
Last Packager: kaolinite
Votes: 28
Popularity: 0.093630
First Submitted: 2012-01-21 11:30 (UTC)
Last Updated: 2026-03-25 10:48 (UTC)

Required by (66)

Sources (10)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »

ishitatsuyuki commented on 2017-03-20 01:31 (UTC)

It's stored in a folder with the name of host triple, which can't be easily determined by the script. Moving them out is very tricky, and that's why I'm trying to avoid it.

spider-mario commented on 2017-03-19 16:46 (UTC)

How easy would you say it is to split it? If it’s significantly easier to build just one package, 4MB doesn’t seem a very big price to pay.

ishitatsuyuki commented on 2017-03-13 04:06 (UTC)

Please cast an opinion on adding analysis as a separate package or not. I have already managed to build one with the analysis data (available with the latest package on my server). They're about 4M in package size. Should I split them? It's necessary for RLS, but their characteristics are like debug symbols.

spider-mario commented on 2017-03-12 13:32 (UTC)

@intelfx, I am not sure that I understand all your issues. Let me try to clarify a few things: - pkgver() (the function) does increase monotonically. I do not change the variable because I want to let users choose when to rebuild (especially as it is an expensive process), and for the most part, changes to the PKGBUILD are merely so that it keeps building—if you weren’t going to rebuild the package to start with, you won’t necessarily want to update just because I fixed building against, say, revision 5e9149d7. (Unless you were actively waiting for the fix, probably.) - submodules in the source array are just for caching between runs of makepkg. If a submodule is absent from the array, it will be fetched normally by the configure script. It is a bit suboptimal bandwidth-wise but it should not break the build. It seems that the build was indeed broken recently, but for another reason: https://github.com/rust-lang/rust/issues/40228. Apparently, it can be fixed either by running `make dist` after `make` (as in Gentoo’s ebuild) or by passing `--disable-dist-src` to configure (as in ishitatsuyuki’s PKGBUILD—I have backported this fix, thanks). Do you still get an error with the fix (or with ishitatsuyuki’s PKGBUILD)?

ishitatsuyuki commented on 2017-03-09 08:36 (UTC)

@intelfx - please try my personal PKGBUILD - https://gist.github.com/ishitatsuyuki/956152c9ee2562e949f55c0181a0c5ee The downloads directory on my server is also regularly updated, once a week or two.

intelfx commented on 2017-03-08 03:58 (UTC)

BTW, the thing does not build -- submodules are not registered nor checked out, and at least the submodule at tools/cargo is missing from source=() altogether.

intelfx commented on 2017-03-08 03:55 (UTC)

Is it possible to make pkgver increase monotonically? Right now there is no way to tell from within an AUR helper whether to rebuild this package.

ishitatsuyuki commented on 2017-02-09 13:17 (UTC)

Can reproduce. Will investigate. Random note: I will update the package a few times a week on my server. https://tatsuyuki.kdns.info/downloads/ (This is NOT a pacman repository but simple file server)

intelfx commented on 2017-02-09 10:18 (UTC)

This package builds rust twice again for me.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »