[PRQ#48783] Deletion Request for openssh-dotconfig-bin
MarsSeed [1] filed a deletion request for openssh-dotconfig-bin [2]: Duplicate of core/openssh, with minimal modification. XDG Base Directory specification support is a fundamental goal of Arch Linux. This modification makes the package adhere less to that, because it hardcodes $HOME/.config as the basedir of .ssh configuration dir, but this does not respect XDG_CONFIG_HOME. If a repo package could be enhanced with better customizability and/or stronger adherence to XDG specifications, one should file an upstream issue and/or an Arch Linux bug with a suggested patch, instead of recreating Arch repo builds on AUR. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/openssh-dotconfig-bin/
Request #48783 has been Rejected by serebit [1]: Not a substantial enough reason for deletion. This package falls under the rule that patched versions of packages in the official repositories are allowed. If you're concerned with how this package is being maintained, an orphan request is preferable. [1] https://aur.archlinux.org/account/serebit/
On Tue, Feb 27, 2024 at 07:26:33PM +0000, notify@aur.archlinux.org wrote:
Request #48783 has been Rejected by serebit:
One thing that the original request missed is that this binary package is actually a pacman package that can be installed with `pacman -U`, meaning the whole thing is a useless unpackaging and repackaging of the same thing. Also, upstream binary releases of OpenSSH [0] are not a thing, this is a binary package generated by the maintainer from openssh-dotconfig [1]; AFAIU, the rules only allow for binary packages provided by upstream. Besides, this type of packages are better suited in a custom pacman repository, which the maintainer is free to share. (BTW, if you download the binary and inspect the `.BUILDINFO` file you'll see it was not compiled in a clean chroot.)
Not a substantial enough reason for deletion. This package falls under the rule that patched versions of packages in the official repositories are allowed.
This is of course reasonable, but I find hard to believe that doing `sed -i 's#\.ssh#.config/ssh/g#'` on every source file and calling it a day constitute "patching" [2], specially on something critical as OpenSSH. This matches strings such as 'host.ssh-ed25519' [3] which may have unintended consequences. Just my two cents. [0] https://www.openssh.com/portable.html [1] https://aur.archlinux.org/packages/openssh-dotconfig [2] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=openssh-dotconfig#n80 [3] https://github.com/openssh/openssh-portable/blob/master/regress/servcfginclu...
participants (2)
-
a821
-
notify＠aur.archlinux.org