[aur-general] Question about PKGBUILD guidelines

[Daniel Berjón Díez]

Hi, Vincent.

I also contributed a wine-based application recently [1] and found the
examples at https://wiki.archlinux.org/title/Wine_package_guidelines
very helpful. Since the wine prefix typically needs to be at least
partially writable, I chose to place the read-only files under /usr/share
and link them from per-user wine prefixes.

Cheers,
Daniel


[1]: https://aur.archlinux.org/packages/adobe-reader-11/ . I would also be
grateful for constructive criticism if anyone wants to have a look.

On Fri, 30 Jul 2021 at 17:18, Vince via aur-general <
aur-general at lists.archlinux.org> wrote:

> Hello,
>
> This is my first time interacting with a mailing list, so please let me
> know if I've done something wrong, or I'm asking in the wrong place.
>
> I plan to submit a binary PKGBUILD for REXPaint, and since it's
> distributed as a portable binary for WINE, I have a couple questions
> about the guidelines:
>
> 1. Is it right that it should be installed into /usr/share?
>
> 2. How do I properly include files that are necessary for use, but not
> included in the upstream source? In my case, this would be a .desktop
> file and a bash script in /usr/bin. My intuition is to use "echo"
> during the prepare() phase, but I was wondering if there was a cleaner
> way to do this.
>
> 3. In accordance with the Nonfree guidelines, I will name my package
> 'rexpaint-bin'. However, since there is no open source version yet, do
> I need to conflict it with 'rexpaint'?
>
> Thanks in advance,
> Vincent
>