Re: Consider releasing separate tarballs for userspace and kernel components

dave penkler <[email protected]> Wed, 6 Aug 2025 13:00:12 +0200
Newsgroups gmane.linux.hardware.gpib.general
Message-ID <CAL=kjP2HXr7Lr_wa4f9qSxBkibUQOuQ=PHo2J0FzsDT09ofJ6Q@mail.gmail.com>
It is going to take a while before the drivers appear in a mainline kernel
shipped by the distros.
I will release a separate user only package when the drivers do appear in
the mainline.
There will be differences between the user package just for mainline
drivers and the  user package co-packaged with the kernel drivers.
In the meantime you can package the user and kernel parts separately as
Michael does for Fedora.
-dave

On Wed, 6 Aug 2025 at 10:03, Matthias Geiger <[email protected]> wrote:

> Am 06.08.25 um 01:09 schrieb Michael K:
> > Hi Matthias,
> >    I package up the Fedora RPMs from a zip of the git repo.
> > (https://copr.fedorainfracloud.org/coprs/vk2bea/GPIB/)
> >
> > The RPM spec defines what and how the packages built from the source.
> > The kernel module is built as a dkms module (so it recompiles when a
> > new kernel is installed).
> > From the SRPM the binary packages are created for installation ....
> >
> > dkms-linux-gpib-4.3.7-30.20250805git0fc6e300.fc42.noarch.rpm
> > guile18-linux-gpib-4.3.7-30.20250805git0fc6e300.fc42.x86_64.rpm
> > linux-gpib-4.3.7-30.20250805git0fc6e300.fc42.x86_64.rpm
> > linux-gpib-devel-4.3.7-30.20250805git0fc6e300.fc42.x86_64.rpm
> > linux-gpib-doc-4.3.7-30.20250805git0fc6e300.fc42.noarch.rpm
> > perl-LinuxGpib-4.3.7-30.20250805git0fc6e300.fc42.x86_64.rpm
> > php-linux-gpib-4.3.7-30.20250805git0fc6e300.fc42.x86_64.rpm
> > python3-linux-gpib-4.3.7-30.20250805git0fc6e300.fc42.x86_64.rpm
> > tcl-linux-gpib-4.3.7-30.20250805git0fc6e300.fc42.x86_64.rpm
> >
> > If the user doesn't want to install the kernel module, they don't
> > install the dkms-linix-gpib package.
> > I presume the same could be done with the debian (apt) build system.
> >
> > Michael
> >
> Hi Micheal,
>
> yeah, I see the point of shipping the dkms package. However, with the
> driver being in mainline soon, I don't see the point of still providing
> it in Debian, because it will be enabled anyway in the kernel.
>
> As all new packages land in unstable first anyway, I think there is
> little benefit for me to enable then in Debian then.
>
> For me this is mostly a tooling problem though, because if I only want
> to provide the userspace tools then I need to jump through some hoops to
> get a tarball only containing those.
>
> Not really a big issue for me; however, I think it's sensible to have
> two separate tarballs given that it will be mainline soon.
>
> --
> Freundliche Grüsse / Best regards
>
> Matthias Geiger
> __________________________________________________________________
> Matthias Geiger
> Werkstudent
> Forschung & Entwicklung/Research & Development
>
> Phone : +49-6441-609-3004
> Email : [email protected]
> URL   : www.wiwa.de
>
> WIWA Wilhelm Wagner GmbH & Co. KG
> Gewerbestrasse 1-3, 35633 Lahnau, Germany
> Besucheranschrift/visitor address:
> Georg-Ohm-Strasse 12, 35633 Lahnau, Germany
>
> AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
> UST-ID Nr: / VAT-No: DE113745802
> Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte
> Weber
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general