https://bugzilla.novell.com/show_bug.cgi?id=215644 ------- Comment #1 from aj@novell.com 2006-10-27 06:05 MST ------- Why is it needed? You propose to add the generic name "kernel" so that one kernel gets installed or what is the proposal? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=215644 ------- Comment #2 from al4321@gmail.com 2006-10-27 06:17 MST ------- what's the purpose of all those patterns after all ? I think patterns exist: For newbie people to easier find packages (and maybe to learn Linux). Advanced Linuxoids doesn't need any patterns... Therefore, show those newbies, that kernel is in "base" package pattern. not just "kernel", but all 3 kernels must be visible there. kernel-default kernel-smp and kernel-bigsmp just like any other "basic" package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=215644 ------- Comment #4 from andreas.hanke@gmx-topmail.de 2006-10-27 11:03 MST ------- AJ, are you sure that this doesn't break the kernel selection done by YaST? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=215644 ------- Comment #6 from andreas.hanke@gmx-topmail.de 2006-10-27 11:52 MST ------- What I mean is that YaST does the kernel selection on its own already. It enforces on its own that a kernel is installed and already displays a big fat warning if the user touches it, even without pattern modifications. (This feature comes from the "+Ins" and "+Del" tags in the repository metadata.) Adding it to the pattern as a dependency causes zypp to consider it when resolving the dependencies. AFAIK, zypp does not know anything about what would be the "right" kernel, it just takes the smallest package that can satisfy the dependency if there are multiple providers. Worth testing is an installation where kernel-bigsmp would be the "right" kernel (it's larger than kernel-default and therefore kernel-default is "better" dependency-wise - unfortunately I don't have the hardware to test this). If it still works afterwards (i.e., it is still selecting kernel-bigsmp for installation), OK. Otherwise I don't really understand the report: The often quoted "newbie" in all these examples should never ever touch the kernel in the first place and simply trust YaST. Users who don't know what a kernel is don't need to see the kernel. I'm not very happy with this change because I think that _not_ enforcing the SUSE kernel package was a good feature for the self-compiling users. During installation, it "just worked" during countless Alphas and Betas without this change, in the installed system, there are already warnings that touching the kernel is dangerous, and uninstalling the SUSE kernel package is a legitimate (unsupported) use case for self-compiling users. The change is not yet synced out, can you tell me whether it uses "Prq", "Prc" or "Psg" now? I'd recommend to use "Psg" if anything at all, it makes the package show up in the list without impact on the depsolver (hopefully). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.