Jo
not stale, probably a dup but most of the others may have been killed by stale bot
I can understand why this could happen with using `sudo`, should be easy to reproduce and fix
Yeah, it's more of an oversight than a bug, but should be easy to implement :+1:
Ok so I see this issue breaks down into two: - ` --cleanafter removes package sources and final product` Yes, since we changed to using `git clean` for cleanafter this...
` --cleanafter removes package sources and final product` is fixed on https://github.com/Jguer/yay/commit/b5b4484c5c68124d996e547e3250e61d822a6062 and in `yay-git`. The other issue will require some heavy refactoring so it has to be thought out...
@Patricol mostly keep your code `gofmt` clean, avoid pulling in more third party dependencies ( unless it is truly justified) and in the case of `showPkgbuildDiffs` return errs instead of...
We don't check svn packages like we do for git so we can't know if they're due for an update, as a closest alternative we could always present svn devel...
For many cases it wouldn't be necessary, for that case maybe pausing yay like we do when the db lock is in place is the best solution EDIT: This is...
Are these `CFLAGS` added in `/etc/makepkg.conf`?
That's a very cool and concrete idea, I like it