Package Details: rust-nightly-bin 1.66.0_2022.10.29-1

Git Clone URL: https://aur.archlinux.org/rust-nightly-bin.git (read-only, click to copy)
Package Base: rust-nightly-bin
Description: Fast, concurrent, safe. The Rust programming language and its package manager, Cargo.
Upstream URL: https://www.rust-lang.org/
Keywords: cargo development rust
Licenses: custom, MIT, Apache
Conflicts: cargo, cargo-git, cargo-nightly, cargo-nightly-bin, rust, rust-docs, rust-git, rust-nightly
Provides: cargo, cargo-nightly, rust, rust-docs, rust-nightly
Submitter: michaelsproul
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 61
Popularity: 0.009831
First Submitted: 2014-04-20 03:15 (UTC)
Last Updated: 2022-10-31 00:35 (UTC)

Required by (4136)

Sources (1)

Latest Comments

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

michaelsproul commented on 2015-01-26 21:23 (UTC)

@haawda: I don't do anything fancy, I just download the Rust makefile, read the version and add the date that the PKGBUILD was created on. The PKGBUILD generator on Github downloads the makefile using a makefile of its own then feeds it to this script: https://github.com/michaelsproul/rust-nightly-archlinux/blob/master/make_pkgbuild.py

haawda commented on 2015-01-26 21:14 (UTC)

Please let me know how you manage to determine the pkgver. I would try to do the same for rust-nightly.

michaelsproul commented on 2015-01-19 19:22 (UTC)

Back to /usr/local we go. Rust's linking *is* still quirky. https://github.com/michaelsproul/rust-nightly-archlinux/issues/13

michaelsproul commented on 2015-01-14 22:44 (UTC)

@Yamaky: Sorry I forgot to answer your original query about syntax highlighting. I don't include syntax files to avoid clogging up the filesystem with extraneous stuff. Every editor also uses its own conventions for syntax file installation. For example, with Vim, I prefer to manage everything with Vundle. Bunch of links on the repo for this package: https://github.com/michaelsproul/rust-nightly-archlinux

michaelsproul commented on 2015-01-14 21:18 (UTC)

@Morn, @Yamakaky: Fixed (upstream Rust seems to be fine with /usr/ now).

Morn commented on 2015-01-14 14:40 (UTC)

Why does this PKGBUILD install into /usr/local/? From https://wiki.archlinux.org/index.php/Arch_packaging_standards: "Packages should never be installed to /usr/local"

Yamakaky commented on 2015-01-11 20:59 (UTC)

Here it is ! I only tried to compile a hello world, as I don't have a bigger project. http://0bin.net/paste/HYBVqfs6gmY51OJB#A4japinzWY6Wo3S8it9onKms7bE8gicmw-KMYZjAjZ6

michaelsproul commented on 2015-01-11 19:33 (UTC)

@Yamakay: I'll get around to it at some point but I'm loathe to fix what isn't broken :P. We've had a whole lot of breakages in the past few weeks, so I figure I'll just let it be stable for a while. Pull requests welcome if you feel like making the changes and testing.

Yamakaky commented on 2015-01-11 14:40 (UTC)

So why don't you do it ? BTW, local MAN_DIR could be set to $INSTALL_DIR/man. Why doesn't you package contain emacs, vim and others syntax files ? They are in src/etc in the github repo.

michaelsproul commented on 2015-01-09 19:47 (UTC)

@Yamakaky: There used to be a problem where installing to /usr/ would give link errors when compiling certain libraries. It seems to be fixed now.

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