Lulu

> it should assume that the user understands what they are doing. Yes it assumes you know yay does not read pkgbuilds > point of allowing editing PKGBUILD anyway? Version...

Right now the clean build wipes out the package then the diffing is done. I'll see about swapping this around, doesn't seem to hard to do.

I've though about doing this but didn't really go for it because you would need to keep an extra file around tracking the commit hashes. But ultimately I don't think...

I don't really see why you'd consider this belonging in config. This file would be caching the last commit we have reviewed. The user does not create it nor modify...

As far as XDG is concerned it says config is for user specific config files and cache is for non essential data. Although what is a config file is not...

Wait, no. Even though we switched to using a ref for tracking, deleting the repo will still delete the ref. This should be closed when cleaning it changed to git...

If that's due to the provides searching, you could try with `--noprovides` it's pointless anyway when using `--noconfirm`. mingw stuff is known to cycle.

>Would you consider automatically adding --noprovides when --noconfirm is used? Sure, it is pointless after all. It was kind of a known bug that there can be some funkiness with...

That's true. Maybe actually fixing the infinite loop when dep cycles are hit should just be done instead.

>Using --noconfirm should definitely not be looking up anything if it could already find a suitable package... What if that suitable package is itself? The problem occurs with dep cycles...