You are lying.
He did not comment about the merge request. You are not quoting him on that because he did not comment specifically on it.
You mentioned the proposed merge to the archey3 dev and asked, among other things, if he would support in any way the archey4 fork. And he replied summarily with "Ship it!". Which means "Go ahead!", in case you misunderstood. On 4 August 2023 11:23:56 GMT+02:00, Gaspard d'Hautefeuille <gaspard@dhautefeuille.eu> wrote:
You are lying.
He did not comment about the merge request. You are not quoting him on that because he did not comment specifically on it.
He said he will no longer develop archey3 and that he will soon archive his repo.
https://github.com/lclarkmichalek/archey3/issues/52#issuecomment-1663777320
Arguments against the merge request:
1) archey3 is on the wiki <https://wiki.archlinux.org/title/Archey3>, not archey4 2) archey3 is maintained in the [extra] repo <https://archlinux.org/packages/extra/any/archey3/>, not archey4 3) archey3-git is maintained on the AUR <https://aur.archlinux.org/packages/archey3-git>, there is no such thing as archey4-git 4) archey3-git is up-to-date with the upstream repo <https://github.com/lclarkmichalek/archey3> 5) archey3-git has 171 votes, archey4 has 16 votes 6) archey3 and archey4 are forks from different authors, so votes & comments should not be merged (stolen) into a whole different package
Argument for deletion:
1) The archey3 author has said he will archive his repo and will no longer maintain archey3 <https://github.com/lclarkmichalek/archey3/issues/52#issuecomment-1663777320>
Arguments against deletion:
1) I contacted the TU Alexander Rødseth that maintains the [extra] archey3 package, he would need to consider maintaining archey4 in [extra] rather than archey3 before we consider for deletion archey3-git 2) When the TU does that, I would need to start maintaining archey4-git, before I submit for deletion archey3-git
On 4 Aug 2023, at 11:17, Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
Maintainer @HLFH also asked the archery3 fork's developer if he plans to get back to it and develop it further, and he replied that he won't be doing so any longer, and in fack he only considers archiving the repo. His "archeying days are over", he said. [a]
The developer also indicated he has no objection to the AUR package merge and of the "stealing" (@HLFH's choice of word) of the votes and comments by the "hippies like MarsSeed" (again @HLFH's characterisation).
Arch repo's archey3 carries the exact same code from 2018 as archey3-git.
Only the archey4 fork is maintained.
Please note that I am not affiliated with archey4 in any way, I have no intention of stealing anything, and I guess being a hippie is not such a bad thing after all. :)
[a]: https://github.com/lclarkmichalek/archey3/issues/52
On 1 August 2023 17:26:43 GMT+02:00, notify@aur.archlinux.org wrote:
MarsSeed [1] filed a request to merge archey3-git [2] into archey4 [3]:
As discussed with maintainer @HLFH in comments 10+ months ago, this application has been superseded by continuation fork archey4. He posted a link to the new AUR package then, so users should be well- informed at this point.
Archey3 has not been developed since 2018. [a]
Arch repo still carries the last archey3 (however, devs would be advised to consider adopting archey4 to [extra]).
Though archey3-git is a VCS package and AUR/archey4 is not, there's no VCS package for the latter but it would still be good to migrate the high number of votes and comments to the successor application's package rather than just deleting them.
AUR/archey3-git is defunct so there's no harm in removing that in favor of archey4.
[a]: https://github.com/lclarkmichalek/archey3/commits/master
[1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/archey3-git/ [3] https://aur.archlinux.org/pkgbase/archey4/