[elrepo-devel] What's the reason for nosrc SRPMs for kernel-lt 4.4.236-1.el7.elrepo.x86_64

Steve Tindall s10dal at elrepo.org
Mon Mar 1 14:40:17 EST 2021


On 3/1/21 2:34 PM, Peter Kahn via elrepo-devel wrote:
> Thanks.  That makes sense to me.  I wanted to make sure I understood.  
> The majority of the source we need are in the devel package anyway for 
> our specific driver build case.
>
> Peter
>
> On Mon, Mar 1, 2021 at 1:44 PM Akemi Yagi <toracat at elrepo.org 
> <mailto:toracat at elrepo.org>> wrote:
>
>     On Mon, Mar 1, 2021 at 10:30 AM Manuel Wolfshant
>     <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote:
>     >
>     > On 3/1/21 7:58 PM, Peter Kahn via elrepo-devel wrote:
>     > > Hi,
>     > >
>     > > Can someone tell me why  kernel-lt 4.4.236-1.el7.elrepo.x86_64
>     has a
>     > > nosrc package instead of a SRPM?  I thought these normally
>     were used
>     > > with 3rdparty vendor restrictions forced the issue and I
>     assumed that
>     > > the kernel-lt would be open source under a GPL license.
>     > >
>     > > Please let me know what's driving this choice.
>     >
>     >
>     > if I were to guess I'd say mere size and the fact that the
>     original is
>     > available in any kernel mirror. there is no benefit in
>     duplicating that
>     > on the ElRepo's mirrors.
>
>     To expand on what wolfy said, what is not included in our "nosrc" SRPM
>     is the original linux code. In your case,
>
>     http://mirrors.coreix.net/elrepo-archive-archive/kernel/el7/SRPMS/kernel-lt-4.4.236-1.el7.elrepo.nosrc.rpm
>     <http://mirrors.coreix.net/elrepo-archive-archive/kernel/el7/SRPMS/kernel-lt-4.4.236-1.el7.elrepo.nosrc.rpm>
>
>     and
>
>     https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.236.tar.xz
>     <https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.236.tar.xz>
>
>     together will create a full source SRPM.
>
>     Akemi
>

To expand just a little more, Yes, kernel srpms are really big, 
especially when mirroring the elrepo archive. There are similar issues 
with repackaged graphics driver srpms. There are also issues with 
exploding the size of local, long term backups when the sources are 
included.

You can install the nosrc.rpm as a user on your system, drop the 
linux-<ver>.tar.xz into ~/rpmbuild/SOURCES/ and then either:

1) build the binary directly via rpmbuild or

2) repackage the nosrc.rpm into a srpm by editing the 
~/rpmbuild/SPECS/<specfile> to comment out the line containing 
“NoSource: <value>”, rebuild the srpm via rpmbuild -bs <specfile> and 
then use the srpm to build the binary in a mock environment.

Steve


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo-devel/attachments/20210301/d99b3dde/attachment.html>


More information about the elrepo-devel mailing list