Jo
Hey @AladW, I'll push an update to yay with `provides` disabled by default and a migration that sets existing installs/configs to false as most were probably left on by default...
As of yay v11.3.0 , `provides` has been disabled by default. I'd move on to https://github.com/Jguer/yay/issues/1781 for continued provides future work
Seems somewhat out of scope for `yay`, news is already on the borderline but if a quickfix is available in the AUR wouldn't the first thing to do be going...
Depends, are the comments parseable or by XML? Because I think I saw it once implemented by page parsing and that's something I would like to avoid
Zawinski's law at work I guess. I'll try and look into it but although go offers great facilities in web parsing, I would really, really like to avoid turning `yay`...
Thinking about it, if we manage not to pull any external library for parsing. The structure is predictable, `http` is already pulled in the project, a simple parser can be...
`yay v11.2.0` should have fixed the issues related with the german locale and the input props. Could you give a try?
Do you use any other locale @douglascamata ?
Seems very interesting, I'll try and take a look at all the references posted. I wouldn't be against including this if we can do it. `yay`'s interfaces have changed enough...
can't reproduce, can you share your `~/.config/yay/config.json`? EDIT: as well if `AURDEST` is present as a env var?