Hi,
Yeah sorry for the lack of context in my merge request (the input box in
the AUR UI is kinda small so i thought it was meant to be kinda concise too)
> I infer you intend to add a lua51-specific subpackage there.
Yep, that's what i meant about the "toggle a comment thing", since i had
to
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 approa
Request #43800 has been Accepted by gromit [1]:
[Autogenerated] Accepted merge for lua51-moonscript into lua-
moonscript.
[1] https://aur.archlinux.org/account/gromit/
+1, go ahead with the merge. :)
On 7 July 2023 15:17:31 GMT+02:00, KokaKiwi wrote:
>Hi,
>
>Yeah sorry for the lack of context in my merge request (the input box in the
>AUR UI is kinda small so i thought it was meant to be kinda concise too)
>
>> I infer you intend to add a lua51-specific subpa
-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 pa
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:
