stays disabled:
* the package is definitely too large (500MB).
* this doesn't use cmake for the installation, so binaries have
a RPATH hardcoded, this is bad.
Add the cargo command to the package. Rust's package management tool is now
included in the package. The rationale for inclusion versus external package
is that the cargo command is closely related to the version of the rustc
compiler, and with the future dependency of the rust build system on cargo
they are closely linked.
The recipe is based on the official github sources, plus patches where
applicable. The tree including patches can be found at
https://github.com/nielx/rust
This recipe is based on the official sources, but has some additional patches.
The tree with integrated patches can be found at https://github.com/nielx/rust
The difference with the recipes for versions 1.9.0 through 1.12.1 is that
this one is based off the "official" rust sources, after Alexander
von Gluck integrated the existing patches and added some additional of his
own. The recipe uses some additional patches to fix the build system (and
some oversights). The complete patched source tree can be found at
https://github.com/nielx/rust
* now uses the short version for vendor and site paths: they are
supposed to be compatible for even version numbers. needs to rebuild
perl modules though.
Note that this recipe depends in on an older version of binutils
(2.26.1), as the current version of binutils (version 2.28.1) has ld
crash in linking the libLTO.so library from the bundled llvm. This is,
by the way, the same on the recipe of llvm-3.8.1 in this repository.
The recipe for 1.9.0 will build the full compiler suite for x86_gcc2,
and it will 'wrap' a binary stage0 compiler for x86_64.
The recipe for 1.10.0 is a complete build.
These recipes don't create the rust_runtime packages. This package
should be recreated at a later point, but we will need to think about
the package naming, as it will be very much possible to have various
runtime libraries running alongside each other.
* rebuild recipes depending on vendor_perl.
* beware though, haikuporter might wrongly select both perl 5.18 and
perl 5.26 in the chroot to satisfy the dependencies.
