notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
All times are UTC
Ukraine
The safest procedure: change your FreshPorts password. Anything you had set before Friday March 24 2023 09:49:20 UTC should be changed. You can read more here: SQL inejection issues fixed and FreshSource code fixes Sorry about the extra work for you.
All known SQL injection issues patched. There is no evidence it was exploited. That doesn’t mean it wasn’t. Please change your password.
non port: lang/rust/files/config.toml
SVNWeb

Number of commits found: 6

Tue, 7 Jan 2020
[ 07:01 tobik search for other commits by this committer ] Original commit   Revision:522316
lang/rust: Simplify do-configure and garbage collect files/config.toml
Mon, 25 Feb 2019
[ 23:09 tobik search for other commits by this committer ] Original commit   Revision:493904
lang/rust: Attempt to fix build on powerpc64

Add change forgotten in r493268.

Pointy hat:	tobik
Sun, 25 Feb 2018
[ 03:10 bdrewery search for other commits by this committer ] Original commit   Revision:462892
Support WITH_CCACHE_BUILD for bundled LLVM
Mon, 27 Nov 2017
[ 18:16 dumbbell search for other commits by this committer ] Original commit   Revision:454983
lang/rust: Remove the LLVM_PORT option

FTR, this option allowed to used LLVM from ports instead of building the
bundled copy.

The problem is that this combination isn't really tested upstream. This
led to regressions which are difficult to diagnose. For instance, in
Rust 1.21.0, the bundled LLVM provided a new API to query the features
supported by the target arch. The equivalent code inside Rust was
removed to use that new API. Unfortunately, building Rust 1.21.0+ with a
copy of LLVM not providing this API didn't failed but instead made that
list of CPU features empty. This resulted in the following obscure build
failure in Firefox:

    error[E0432]: unresolved import `x86::sse2`

To avoid future pain for both end users and maintainers, we decided to
remove that option. Yes, it will increase the (already long) time to
build Rust, but it should save time wasted on debugging what is not
really supported anyway.

PR:		223342, 223300
Reported by:	Many users
Fri, 15 Sep 2017
[ 18:01 dumbbell search for other commits by this committer ] Original commit   Revision:449914 (Only the first 10 of 12 ports in this commit are shown above. View all ports for this commit)
lang/rust: Install Cargo + use bundled crates

This port now provides Cargo. This is the recommended now because Cargo
won't be provided separately in the future.

To build Cargo, we set `extended = true` in `config.toml`. As a side
effect, this flag also installs Rust source code. The port has a new
`SOURCES` option (disabled by default) to keep those sources.

As a consequence of this, `devel/cargo` is removed. Several ports
and Makefiles in Mk were updated to depend on `lang/rust` instead of
`devel/cargo`.

The other big change in this patch is the use of the bundled crates,
instead of relying on Cargo's registry (which was part of the distfiles,
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Fri, 28 Jul 2017
[ 10:18 dumbbell search for other commits by this committer ] Original commit   Revision:446815
lang/rust: Update to 1.19.0

The main change in the port is the switch from configure+make to the
`x.py` build script. This is the recommended way of building Rust. It
takes a configuration file, `config.toml`, which, in the port case,
indicates:

 * where to install things;
 * which release channel to use;
 * where to find Python and llvm-config;
 * if documentation should be also built.

The build process should now honor ${MAKE_JOBS_NUMBER} instead of always
using all available CPU cores.
(Only the first 15 lines of the commit message are shown above View all of this commit message)

Number of commits found: 6