Re: mktool support for fetch

[Benny Siegert <bsiegert%gmail.com@localhost>]

> Am 24.08.2024 um 19:52 schrieb Alistair Crooks <alistaircrooks%gmail.com@localhost>:
> 
> 
> 
> On Sat, 24 Aug 2024 at 10:37, pin <voidpin%protonmail.com@localhost> wrote:
> >  I'll keep it in TritonDataCenter/pkgsrc.  There is no shortage of
> >  patches there that folks aren't keen on ;-)
> 
> This is a huge disappointement.
> Guess, I need to add the hooks locally.
>   
> I don't think anyone is ever going to suggest that rust tools take over completely from the shell/awk/sed/unix tool scripts that we have always had - they give pkgsrc portability, allowing use of pkgsrc on lotsa platforms, and bringing much needed utilities to platforms which would otherwise not have them. At the same time, I'd love to see faster, more efficient alternatives, which, should the platform have a rust toolchain available, could be used in place of the scripts. Or to build the outliers like grafana which stretch OS limits some (and maybe OS limits are difficult to change for some platforms). Anyway, I'd like to see an option for both, and I'd like to have this available to all pkgsrc users

Fully agree. I see the slippery slope argument but we have bulk builds for keeping things in check. The bulk builds are not going to use any of the Rust tooling, so packages that only work with that are broken by definition.

I for one would like to see the hooks added to pkgsrc but as opt-in. This is what had been proposed anyway.

Keeping the juicy improvements local to TritonDataCenter is a bit of a disappointment.

— 
Benny