Dewayne Geraghty writes:
> I don't use anything that requires rust but for some reason developers
> don't provide a choice... so I've branched /usr/ports to track this
> practice and retain reasonable build times. Point? Its not just docs that
> you'll need to accommodate. :/
Why not DEFAULT_V
On Oct 9, 2023, at 16:28, Charlie Li wrote:
> Mark Millard wrote:
>> My understanding is that building a devel/llvm* these days requires
>> building rust first, via needing to build python things (for
>> documentation purposes?), that in turn need rust to have been built
>> first. Last I knew, tr
Hi Mark, yes it seems that some maintainers are letting dependencies
bloat. A few weeks ago I had to rebuild samba4.13 (on FBSD 12.4) and it
required rust to build(!). This was due to a documentation requirement to
use py-poetry . Fortunately the py-poetry maintainer (I think) realised
and adjus
Mark Millard wrote:
My understanding is that building a devel/llvm* these days requires
building rust first, via needing to build python things (for
documentation purposes?), that in turn need rust to have been built
first. Last I knew, trying to disable the llvm* DOCS option in a
normal way did
Charlie Li wrote on 2023-10-09 15:30:33 + :
> lang/rust: resurrect PORT_LLVM as a non-default OPTION
>
> Rust uses LLVM for code generation [0] and bundles their own copy of a
> release that they fully support in relation to the rest of rustc. This
> however adds to an al
