Le 03/07/2023 à 22:20, james smith a écrit :
> one last question before adding it to the aur 1) can I have multiple 
> emails for the maintainer so that I have a backup incase one email 
> goes down 2) if the package goes to the main repos will I be the 
> maintainer or will the person who brought it to the main repos be the 
> maintainer
1) I'm not sure what you mean by "goes down". The email you filled in is 
a gmail address, I doubt it will often (if not "ever") go down :p
If you meant that as if you ever decide to take that email down for any 
reason, then you can just update your email address in the PKGBUILD. 
Anyway, you /could/ have multiple emails in the PKGBUILD but the idea 
here is mostly to have a way to contact you directly if you're not 
responding to comments on the package's AUR webpage. One email address 
is fine :)
2) AUR packages are contributions made to the Arch Linux project and 
does not "belong" to the person who submitted or maintain them. In that 
sense, if an AUR package is moved to the main repos, the Arch package 
maintainer who did it becomes the new maintainer but you'll be listed as 
a "contributor" in the PKGBUILD.
However, this cannot happen with that particular package because VCS/git 
packages are not allowed on the main repos, so "lemoa*-git*" won't ever 
go to the main repos.
>
> On Mon, Jul 3, 2023 at 7:12 AM Robin Candau <antiz@archlinux.org> wrote:
>
>     Le 03/07/2023 à 07:00, james smith a écrit :
>>     Now after making those changes running it, it doesn't correctly
>>     git clone Neither source directory 'source' nor build directory
>>     'build' contain a build file meson.build.  and I believe this
>>     command is the culprit |printf "%s.r%s.%s" "$(git describe --tags
>>     --abbrev=0 | sed 's/^v//')" "$(git rev-list --count HEAD)" "$(git
>>     rev-parse --short HEAD)"| because it git clones it "empty" as
>>     just the .git folder. Not all files https://bpa.st/XA5JI
>>     apologies for the redundant questions
>     The culprit is that you copied the "meson setup" command from the
>     wiki without actually adapting it to your case. The "source" and
>     "build" statements in it have to be replaced by the actual
>     "source" and "build" directory of the repo you're trying to build
>     (notice how "source" and "build" are written in /italic/ in the
>     wiki [1], indicating that they have to be adapted to your case).
>     Also, you have to `cd` first to the cloned repo before launching
>     build instructions.
>
>     Finally, "libadwaita" should be an actual dependency (not simply a
>     make one) I think.
>
>     Here's a fixed PKGBUILD:
>     https://bpa.st/BTXWE
>
>     I allowed myself to also make some small "best practices" and
>     "style" improvements to it as well: re-add the trailing ".git" at
>     the end of the source, switch to sha256 instead of md5 (I know the
>     checksum is skipped there, but better take the habit to use a
>     stronger algorithm for the potential future), better indentation
>     in functions, etc...
>
>     [1]
>     https://wiki.archlinux.org/title/Meson_package_guidelines#Using_meson_binary_directly
>
>     -- 
>     Regards,
>     Robin Candau / Antiz
>
-- 
Regards,
Robin Candau / Antiz