Why is package maintainance pending for so long, is there a way to support Ronald in any kind? I also thought about adding a new package to the AUR for the enlightenment major releases, but this does not seem to be a solution and bloats the AUR. Using enlightenment-git is too bleeding edge in my opinion, and sometimes does not compile or ends in unwanted effects (my system crashed the last time when doing some history search in xterm sessions?!). So thats not an option.
]]>/deleted.
]]>thanks for the package update.
but also sad that look like got forgoten again it was so good at the start.
I don't expect it to change TBH. E isn't a popular DE with devs afai understand and unless someone decides to take over the packages we will have to update on our own.
I will also add a terminology PKGBUILD once 1.1.0 is released.
]]>In case of bugs report them at phab.enlightenment.org.
]]>Not everyone is interested in editing or maintaining random packages, [...]
Although I welcome the proposed push towards simplifying things for potential contributors, here it's precisely about editing packages. As a regular user, the only option so far is to nudge the maintainer and hope they fix a package. In many cases, there appears to be only a single maintainer for a package. Making it so that it's easier to become a TU (or even creating other new tasks for potential contributors) most likely won't change anything about that.
The way I perceive it (I may be wrong, but I'm certainly frustrated), it's currently:
Create packages for software that haven't been packaged yet (increasingly hard) or adopt orphan packages in the AUR
Maintain packages in the AUR that are popular enough to brag about
Find somebody who's willing to be a sponsor
Be voted as a TU
Somehow (?) become a developer
Maybe get permission to fix that one packaging bug