Alad Wenter
Alad Wenter
I don't think this can be implemented in a tool that operates on the level of the git repository (committer and AUR maintainer are not necessarily the same). So a...
> Or maybe even include it in the created .diff files as a separate virtual file? That sounds like a reasonable idea, though I guess it could only be implemented...
Yes, this could definitely work. The `userdata` could be taken from the command-line, `git diff`'ed, and saved in the `aur-view` directory. And the contents are then generated in `aur-sync`.
Thanks for the report. As you might have expected from the very late reply, this is non-trivial to implement. https://github.com/AladW/aurutils/issues/350#issuecomment-383278892 might give some ideas.
https://github.com/AladW/aurutils/issues/836#issuecomment-949909329 Reopening this issue.
With an actual dependency graph available (through `aur-sync--ninja`), this should be possible to implement.
Added, thanks for the reminder.
Upstream issues for `repose`: - [x] **repose** performance issues with large databases https://github.com/vodik/repose/issues/42 - [ ] **repose** does not take absolute paths to packages https://github.com/vodik/repose/issues/49 - [ ] **repose** failure...
I guess it can be handled in a satisfactory way from the caller, unlike any of the other "dead end" issues. I moved it to "closed".