Multiple packages in PKGBUILD and creating groups?
Hello, I have two questions, I merged it into one post to prevent people complaining about Polarian Notifications (aka me popping up on their email every 5 mins). Does anyone have a good reference I can use to properly make a multi-package PKGBUILD, I have no experience doing this and I want to stick to conventions, and the PKGBUILD ArchWiki page does not seem to cover it. Secondly, is it possible to create PKG groups within the AUR, I would like to group a few packages together, but I am unsure if I am allowed, or able to do this, unless it is added to an official repository. Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On 31-01-2023 10:10, Polarian wrote:
Hello,
I have two questions, I merged it into one post to prevent people complaining about Polarian Notifications (aka me popping up on their email every 5 mins).
Does anyone have a good reference I can use to properly make a multi-package PKGBUILD, I have no experience doing this and I want to stick to conventions, and the PKGBUILD ArchWiki page does not seem to cover it.
Secondly, is it possible to create PKG groups within the AUR, I would like to group a few packages together, but I am unsure if I am allowed, or able to do this, unless it is added to an official repository.
Thanks,
Hi, Those are 2 questions that have very little in common . I'll focus on the multi-package part. Split / multi-package PKGBUILDs are a solution to a problem. Any PKGBUILD with one package function (singular) can be transformed into a split package. However if the singular PKGBUILD has no problems, there's no need to do that. Incase a split package can not be transformed back into a singular PKGBUILD, that package should probably not be written as a split package but as separate multiple packages. One example : Programs using llvm as compiler need all of it at compiletime, but at runtime they only need a small part of it to function . Upstream didn't distinguish beteen compiletime & runtime parts, archlinux devs decided to split the runtime parts off to a separate package. look up llvm & llvm-libs in [extra]. LW
On 31-01-2023 11:57, Lone_Wolf wrote:
Upstream didn't distinguish beteen compiletime & runtime parts, archlinux devs decided to split the runtime parts off to a separate package.
forgot to include the word function . The whole sentence should be : Upstream didn't distinguish between compiletime & runtime parts, archlinux devs decided to split the runtime parts off to a separate package function .
Hello, Thanks for the help, however do you have any advice on the second part of my question (grouping packages in the AUR). Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On Tue, Jan 31, 2023 at 1:10 PM Polarian <polarian@polarian.dev> wrote:
Hello,
I have two questions, I merged it into one post to prevent people complaining about Polarian Notifications (aka me popping up on their email every 5 mins).
Does anyone have a good reference I can use to properly make a multi-package PKGBUILD, I have no experience doing this and I want to stick to conventions, and the PKGBUILD ArchWiki page does not seem to cover it.
/usr/share/pacman/PKGBUILD-split.proto
Secondly, is it possible to create PKG groups within the AUR, I would like to group a few packages together, but I am unsure if I am allowed, or able to do this, unless it is added to an official repository.
Just use pkgbase as the git repo name. Example: https://aur.archlinux.org/pkgbase/psiphon-tunnel-core
Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
Hello, Thanks for the links, I will check them out now -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
participants (3)
-
eNV25
-
Lone_Wolf
-
Polarian