Re: It's not Rust, it's FreeBSD (and LLVM)
- Reply: Warner Losh : "Re: It's not Rust, it's FreeBSD (and LLVM)"
- In reply to: Olivier Certner : "Re: It's not Rust, it's FreeBSD (and LLVM)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 11 Sep 2024 08:47:20 UTC
Am 2024-09-10 21:41, schrieb Olivier Certner: >> 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 consider src, ports, and docs as separate repos, not as one repo (we can branch them separately, that's the point of distinction for me). With that POV I do not think it is pragmatic to have the toolchain in the same repo. I understand that it's convenient and less painful, and pragmatic in regards to what you have mentioned, to keep it within a repo in our control (like now, just in parallel to ports/src/doc). Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF