[aur-general] Question about PKGBUILD guidelines
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
Hi Vince, About number 2, you can include the files alongside the PKGBUILD in the git repo you push to the AUR, then add them to your "sources" array. Then, in package(), you can use the "install" or "cp" command to move the files to their desired location in the package. Welcome to the mailing list! Yash Karandikar d5c4 1cbc 071b 41b3 f235 da13 f01e 92cd 2390 f369
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@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
Hi guys, same here, in my case it's Racer [1]. The start script is included as source (I didn't supply a desktop file because I didn't find a suitable icon). Also glad about constructive feedback! All the best, Michael [1] https://aur.archlinux.org/packages/racer-cg/ Am Fr., 30. Juli 2021 um 17:39 Uhr schrieb Daniel Berjón Díez via aur-general <aur-general@lists.archlinux.org>:
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 21-07-30 15:18, Vince via aur-general 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.
For a shorter feedback loop, hop onto the #archlinux-aur IRC channel and ask for some advice. There's generally always people around willing to critique potential packages.
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?
Binaries go into /usr/bin, not sure how Wine specific binaries are done though.
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.
Add them to the sources array and install them in the package function. One of my packages (nanosaur[0]) may be of some help.
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'?
If the sources aren't available[1], you don't have to.
Thanks in advance, Vincent
Welcome to the mailing list :) [0]: https://aur.archlinux.org/packages/nanosaur [1]: https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submissi... -- George Rawlinson
participants (5)
-
Daniel Berjón Díez
-
George Rawlinson
-
Michael Kogan
-
Vince
-
Yash Karandikar