I am just someone maintaining a package in the AUR and not an admin.
Perhaps a descriptive package name like "thrive-life-planner" maybe
accepted.
However, if you set
`conflicts=('thrive')` in your PKGBUILD, that will create problems.
The best way to avoid this is to rename your app completely, but that may
not be possible in some cases.
I am interested in seeing how this issue will be handled. I just checked
the AUR Submission Guidelines, and there seem to be no guidelines for this
situation.
Regards,
H
On Mon, 9 Feb 2026, 6:11 am Fermín Olaiz, <[email protected]> wrote:
> Hey there! I'm reaching out because I didn't find any reference to the
> topic in the wiki [1] or in the discussion page.
>
> I'm making a package around an app called Thrive [2], but I found that
> there is already a completely different package with the same name. For
> the package I'm making there's an app and a cli version, so I'm guessing
> in this case they could perfectly be named `thrive-app` and `thrive-cli`.
>
> In any case, with a growing number of packages in the AUR, it would be
> reasonable to think this kind of things will happen more frequently.
>
> Is there any guideline or ideas for this? Should a discussion (maybe
> RFC) be started?
>
> Thanks!
>
> Fermín Olaiz.
>
>
> [1]
> https://wiki.archlinux.org/title/Arch_package_guidelines#Package_naming
>
> [2] https://github.com/horia141/thrive
>
>
