On 3/1/23 20:43, a...@moritz.poldrack.dev wrote:
Hi, I think this does not apply then. As shown by the -git suffix, this
is a development package, and having notmuch included or not can lead to
differences. Especially when aerc's merge of the notmuch and maildir
workers is completed. For this reason, I think the package should stay
in one way or another. Please advise on how it would be acceptable to
make this compile-time differentiation possible with one PKGBUILD.
Also, if possible, please include more details when submitting a request
like this. Copy-Pasting the reason might be efficient, but seeing
multiple submissions, all with the same generic text did strike me as
rather odd to say the least. Apologies for suggesting that this might be
used in an abusive manner, but I had the displeasure with bad-faith
actors before. Hope all is well :)
Kind regards,
Hello. Sorry for lack of details. I was helping TUs with this little raid.
Such packages are considered duplicates (already present in official repos) by
submission guidelines. Simply altering the build options (in sake of just
dropping dependencies etc.) is not enough to count as a standalone package
variation. This is what I was said.
As for the git part, yeah, this may be controversial. But
https://aur.archlinux.org/packages/aerc-git already exist, so I can't really
tell is it appropriate to have both.
Anyway, it is up to TU to decide. This request still may be rejected.
