Arch Linux User Repository

LLVM 4.0 is in [testing]. DO NOT UPGRADE.

Checkout my unsigned repository for packages built with my own, diverged PKGBUILD: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#rust-git This is updated on a best effort basis. Normally I rebuild every week, but sometimes I could be busy. Feel free to mail me to request an update. You're welcome to use this for reference: https://gist.github.com/ishitatsuyuki/956152c9ee2562e949f55c0181a0c5ee

I have upgraded my PKGBUILD. No more build twice problems, and it now splits things by dist packages. https://gist.github.com/ishitatsuyuki/956152c9ee2562e949f55c0181a0c5ee

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.

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.

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.

@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)?

@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.

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.

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.