U-turn: +1 for the merge. @KokaKiwi, sorry, I didn't know you were the maintainer of the target package, lua-moonscript. You also didn't say the latter is a split package for different Lua versions. I infer you intend to add a lua51-specific subpackage there. Now I see that is the right approach. Also the old source package lua51-moonscript is an outdated orphan. On 7 July 2023 14:56:25 GMT+02:00, Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
-1 for merge.
Custom-editing PKGBUILDs of AUR packages is not something users should regularly do.
If they are compelled to turn to such measures, that means either there is a packaging error, or there needs to be a different variant of that package.
Like in this case: A separate moonscript package for main lua dependency, another one for lua51.
Let's keep both packages as they are.
This is not Gentoo where you can parameterize the build of the same package source via USE flags.
On 7 July 2023 10:56:45 GMT+02:00, notify@aur.archlinux.org wrote:
KokaKiwi [1] filed a request to merge lua51-moonscript [2] into lua- moonscript [3]:
lua51-moonscript can be handled by the lua-moonscript AUR package (just need to toggle a comment)
[1] https://aur.archlinux.org/account/KokaKiwi/ [2] https://aur.archlinux.org/pkgbase/lua51-moonscript/ [3] https://aur.archlinux.org/pkgbase/lua-moonscript/