@sommerfeld - thanks, similar position myself but for mcedit. Builds fine now.
Sorry for the delay in fixing the PKGBUILD as I was on vacations.
I should give a little backstory: as one can see in the PKGBUILD I am not the original maintainer. The previous one was @foxboron, a known TU with a very active reddit and irc presence.
I hate python2 and hope it eventually dies, but this package is a dependency for a package I care about (acestream-engine) and there is nothing I can do to change that.
When this package disappeared from the AUR, I hopped on #arch on IRC, chatted a bit with @foxboron and found out that he was the one who purposely deleted it since python2 is officially EOL in 2020. He said that if I cared enough, I could take it on, reuse the PKGBUILD from the python3 version (python-xlib), do a 's/python/python2' and publish it on the AUR with my account.
That is exactly what I did. It's my first every AUR package, so I had to learn some stuff. I noticed right away that the 'cd "$pkgname-$pkgver"' was wrong and caused a failure, so I patched the PKGBUILD right away but unfortunately forgot to push the change to the AUR and went on vacation for 2 weeks...
Let's see how this holds up now. I appreciate any help and suggestions.
@the_z0id: edit lines 20 and 25 in the PKGBUILD
Change:
cd "$pkgname-$pkgver"
to
cd "python-xlib-$pkgver"
Need to rename the filename.
Knowing this, is there a fix?
fails because the directory is python-xlib-0.26, not python2-xlib-0.26
can confirm, the file name is wrong
cd "$pkgname-$pkgver" fails because the directory is python-xlib-0.26, not python2-xlib-0.26.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
Sorry for the delay in fixing the PKGBUILD as I was on vacations.
I should give a little backstory: as one can see in the PKGBUILD I am not the original maintainer. The previous one was @foxboron, a known TU with a very active reddit and irc presence.
I hate python2 and hope it eventually dies, but this package is a dependency for a package I care about (acestream-engine) and there is nothing I can do to change that.
When this package disappeared from the AUR, I hopped on #arch on IRC, chatted a bit with @foxboron and found out that he was the one who purposely deleted it since python2 is officially EOL in 2020. He said that if I cared enough, I could take it on, reuse the PKGBUILD from the python3 version (python-xlib), do a 's/python/python2' and publish it on the AUR with my account.
That is exactly what I did. It's my first every AUR package, so I had to learn some stuff. I noticed right away that the 'cd "$pkgname-$pkgver"' was wrong and caused a failure, so I patched the PKGBUILD right away but unfortunately forgot to push the change to the AUR and went on vacation for 2 weeks...
Let's see how this holds up now. I appreciate any help and suggestions.