Re: It's not Rust, it's FreeBSD (and LLVM)

> IMO it doesn't hurt to move the toolchain out of src (...)
> 
> (...) I would not want to move everything to ports (...), but I would not
> mind having a ports-like approach for src (...) 

To clarify and be sure we are on the same page, I also don't mind what you describe *provided* there is appropriate tooling to easily:
- Get all the code part of base, and not only for building it.
- Navigate its history, both for code changes but also integration in base for upstream projects (upstream history is nice, but not enough).

In other words, I insist on having the same ease of use that we have today with everything in a single repository.  Being able to just build base *is not enough*.  Else, moving things to ports is going to cause important pain for several use cases such as code inspection and auditing, collaborative maintenance of code moved to ports, understanding why/whether some changes have impact on some components, system consistency, etc.

> (I don't know if pkgbase fits this or not, I haven't looked at it, but if I
> can define a pkg repo for base and populate it from e.g. "make pkgrepo
> DESTDIR=xxx" or similar and then just need to run pkg upgrade that would be
> nice).

I haven't used it personally, but from what I read, I expect what you describe to be exactly its main supported use case.

Thanks and regards.

-- 
Olivier Certner