[aur-general] Package splitting
Hi all, I'm planning to package pf_ring for archlinux. pf_ring has several components: - Common kernel module - Several kernel drivers for some network cards - Userland lib and includes - Some pf_ring capable softwares (tcpdump, libpcap, snort...) I'm wondering how to split this into several packages... Does the following look OK? - pfring-module-svn for kernel module - pfring-driver-xxx-svn for kernel drivers (one per card driver: e1000e igb tg3 ...) - pfring-svn for userland (lib and includes) - snort-pfring-svn, tcpdump-pfring-svn... for pf_ring capable softwares (with conflicts=snort, conflicts=tcpdump...) Thanks, -- Gwenn
Gwenn Gueguen <gwenn+aur@beurre.demisel.net> writes:
I'm wondering how to split this into several packages...
Does the following look OK?
- pfring-module-svn for kernel module
- pfring-driver-xxx-svn for kernel drivers (one per card driver: e1000e igb tg3 ...)
- pfring-svn for userland (lib and includes)
- snort-pfring-svn, tcpdump-pfring-svn... for pf_ring capable softwares (with conflicts=snort, conflicts=tcpdump...)
Hi, That looks fine. Are you thinking of writing a split PKGBUILD? If so, realize that the AUR doesn't support them. You will need to write a separate PKGBUILD for each component. -- Chris
Am Thu, 18 Nov 2010 10:55:20 +0000 schrieb Christopher Brannon <chris@the-brannons.com>:
That looks fine. Are you thinking of writing a split PKGBUILD? If so, realize that the AUR doesn't support them. You will need to write a separate PKGBUILD for each component.
There's a workaround for this even if it would be better if AUR would support split packages natively without needing a workaround. See the demo package splittest: http://aur.archlinux.org/packages.php?ID=42514 Heiko
On 18 November 2010 21:43, Heiko Baums <lists@baums-on-web.de> wrote:
Am Thu, 18 Nov 2010 10:55:20 +0000 schrieb Christopher Brannon <chris@the-brannons.com>:
That looks fine. Are you thinking of writing a split PKGBUILD? If so, realize that the AUR doesn't support them. You will need to write a separate PKGBUILD for each component.
There's a workaround for this even if it would be better if AUR would support split packages natively without needing a workaround.
See the demo package splittest: http://aur.archlinux.org/packages.php?ID=42514
That works. And also you can include a generic/barebones PKGBUILD which tells the user to rename a PKGBUILD.split (the real PKGBUILD) to PKGBUILD.
participants (4)
-
Christopher Brannon
-
Gwenn Gueguen
-
Heiko Baums
-
Ray Rashif