Bug 340720 - rename linux-kernel-headers
Summary: rename linux-kernel-headers
Status: VERIFIED FIXED
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Development (show other bugs)
Version: Factory
Hardware: All Linux
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: Petr Baudis
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-09 18:54 UTC by Jan Engelhardt
Modified: 2009-12-14 13:45 UTC (History)
2 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Engelhardt 2007-11-09 18:54:22 UTC
A lot of newbies think that linux-kernel-headers are required for kernel module building and accordingly get confused when its version number is not the same as kernel-$yourFlavor and come up with blame on lkh.rpm.
Suggestion to rename linux-kernel-headers to e.g. glibc-linux-headers.
Comment 1 Petr Baudis 2007-11-09 20:07:34 UTC
Can you quantify "a lot"? Back it up by some references e.g. to mailing lists, IRC logs?

Both Debian and Fedora use kernel-headers package name. It is explained in package description that these are userspace headers. Also, if we keep renaming the package all the time (it was kernel-headers before, linux-kernel-headers now), that will be troublesome too. Also, I can't think of any package name that wouldn't be less accurate than the current one (the kernel headers don't have anything to do with libc per se).
Comment 2 Jan Engelhardt 2007-11-09 20:54:13 UTC
A lot := so much that it finally itched me to submit a bugreport
I would have to start collecting statistics first, because forum posts and irclogs are recycled on a regular basis.

Keep renaming: could have stuck to the original "lx_include" name. :-)
Few people actually look at the package descriptions.

Perhaps "linux-includes" would do?
Comment 3 Jan Engelhardt 2008-07-08 21:41:36 UTC
Jul 08 2008, #suse

23:22 < dartelin> i'm trying to install vmware-workstation
23:22 < dartelin> and it need the kernel-headers
23:27 < dartelin> tacit, the kernel-headers are not the same version as the running kernel
23:28 < dartelin> running kernel is 2.6.25-9-0.2 and kernel-headers in the repo are version 2.6.25-8.1
Comment 5 Jan Engelhardt 2008-07-13 18:57:21 UTC
http://forums.opensuse.org/applications/389705-kernel-version-mismatch-headers-source.html

and #suse
20:54 < martman:#suse> im runing kernel 2.6.25.5-1.1-pae but my headers 
                       arelinux-2.6.25.9-0.2, is there a easy way to get them 
                       to match?
Comment 7 Jan Engelhardt 2008-10-23 13:22:47 UTC
Hey, don't let this bug time out.
Comment 8 Daniel Gollub 2008-12-20 21:11:09 UTC
Jan, this is a very soft-topic.

I would suggest to let the package maintainer decide if this should get renamed or not. Maybe Petr got convinced already by your references.

Petr, are the references provided by Jan enough to rethink a renaming?
Or do you want to stay with linux-kernel-headers?

(I see for both ways advantages and disadvantages - but it's up to Petr to decided)
Comment 9 Jan Engelhardt 2009-02-18 16:57:01 UTC
ping ;)
Comment 10 Petr Baudis 2009-09-14 22:04:06 UTC
Oops, stale NEEDINFO, sorry. :(

I have nothing against a rename personally, but it's a change of existing practice and I think someone higher in our food chain should ack this. ;)

Debian uses linux-libc6-dev, I think linux-glibc-dev would be fine name.
Comment 11 Stephan Kulow 2009-09-15 08:07:41 UTC
we do not have any -dev packages :)

but now is a really a bad time to do such a change ;(

I'm fine with linux-glibc-devel for 11.3 though.
Comment 12 Petr Baudis 2009-11-13 22:32:40 UTC
So, 11.2 is past us... I have now committed the renamed package linux-glibc-devel in Base:System - Coolo, can you please advise how to propagate this to Factory, and when is it safe to remove linux-kernel-headers?
Comment 13 Stephan Kulow 2009-11-16 10:03:38 UTC
I think Dirk pushed it forward - and it can build safely, so we can later switch the project config once we see the expansion error because both packages provide the old name.
Comment 14 Petr Baudis 2009-11-19 12:08:49 UTC
Ok, so marking this fixed.