[New: openFATE 311446] Split Kernel rpms from Tumbleweed repo
Feature added by: Bill P (google01103) Feature #311446, revision 1 Title: Split Kernel rpms from Tumbleweed repo openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Bill P (google01103) Partner organization: openSUSE.org Description: Currently the Tumbleweed repo contains both app and kernel rpms, I propose that the Tumbleweed project be split into 2 repos - kernel and apps. The reason for this being that updating a kernel can be much more problematic/disruptive to an existing install compared to just updating apps. I admit this might be an unwarranted personal concern but it gives me pause when considering using the Tumbleweed repo. Locking the kernel rpms would also lock the oss repo's kernel updates which would not be a wise move as oss kernel updates have defined pupose (stability, security). -- openSUSE Feature: https://features.opensuse.org/311446
Feature changed by: Jonas Rüdiger (JSowieso) Feature #311446, revision 2 Title: Split Kernel rpms from Tumbleweed repo openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Bill P (google01103) Partner organization: openSUSE.org Description: Currently the Tumbleweed repo contains both app and kernel rpms, I propose that the Tumbleweed project be split into 2 repos - kernel and apps. The reason for this being that updating a kernel can be much more problematic/disruptive to an existing install compared to just updating apps. I admit this might be an unwarranted personal concern but it gives me pause when considering using the Tumbleweed repo. Locking the kernel rpms would also lock the oss repo's kernel updates which would not be a wise move as oss kernel updates have defined pupose (stability, security). + Discussion: + #1: Jonas Rüdiger (jsowieso) (2011-03-20 19:47:01) + Tumbleweed's kernel didn't work with the official Nvidia driver + package, last time I tried, and I don't want to build it myself every + update. It would be nice to be able to stick with the official kernel, + as an option. -- openSUSE Feature: https://features.opensuse.org/311446
Feature changed by: Robert Davies (robopensuse) Feature #311446, revision 3 Title: Split Kernel rpms from Tumbleweed repo openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Bill P (google01103) Partner organization: openSUSE.org Description: Currently the Tumbleweed repo contains both app and kernel rpms, I propose that the Tumbleweed project be split into 2 repos - kernel and apps. The reason for this being that updating a kernel can be much more problematic/disruptive to an existing install compared to just updating apps. I admit this might be an unwarranted personal concern but it gives me pause when considering using the Tumbleweed repo. Locking the kernel rpms would also lock the oss repo's kernel updates which would not be a wise move as oss kernel updates have defined pupose (stability, security). Discussion: #1: Jonas Rüdiger (jsowieso) (2011-03-20 19:47:01) Tumbleweed's kernel didn't work with the official Nvidia driver package, last time I tried, and I don't want to build it myself every update. It would be nice to be able to stick with the official kernel, as an option. + #2: Robert Davies (robopensuse) (2011-07-18 11:50:46) + It is simple to keep the 11.4 kernel and not upgrade to a newer stable + kernel. Just enable multiversion kernel in zypp.conf, use "zypper up" + in general and it will say, the Tumbleweed kernel is not being + upgraded. It is only on "zypper dup" when you allow vendor change, that + the Tumbleweed kernel package is installed. The idea of Tumbleweed repo + is to collate the latest stable FOSS updates, removing packages to + seperate repos to suit users of proprietary drivers, inconveniences the + many who want to try newer kernels (and if they use proprietary + graphics re-build the module). There is absolutely no need to split out + the kernel packages. -- openSUSE Feature: https://features.opensuse.org/311446
Feature changed by: Karl Cheng (qantas94heavy) Feature #311446, revision 4 Title: Split Kernel rpms from Tumbleweed repo - openSUSE Distribution: Unconfirmed + openSUSE Distribution: Rejected by Karl Cheng (qantas94heavy) + reject reason: New Tumbleweed is completely separate from the stable + Leap distribution. Priority Requester: Desirable Requested by: Bill P (google01103) Partner organization: openSUSE.org Description: Currently the Tumbleweed repo contains both app and kernel rpms, I propose that the Tumbleweed project be split into 2 repos - kernel and apps. The reason for this being that updating a kernel can be much more problematic/disruptive to an existing install compared to just updating apps. I admit this might be an unwarranted personal concern but it gives me pause when considering using the Tumbleweed repo. Locking the kernel rpms would also lock the oss repo's kernel updates which would not be a wise move as oss kernel updates have defined pupose (stability, security). Discussion: #1: Jonas Rüdiger (jsowieso) (2011-03-20 19:47:01) Tumbleweed's kernel didn't work with the official Nvidia driver package, last time I tried, and I don't want to build it myself every update. It would be nice to be able to stick with the official kernel, as an option. #2: Robert Davies (robopensuse) (2011-07-18 11:50:46) It is simple to keep the 11.4 kernel and not upgrade to a newer stable kernel. Just enable multiversion kernel in zypp.conf, use "zypper up" in general and it will say, the Tumbleweed kernel is not being upgraded. It is only on "zypper dup" when you allow vendor change, that the Tumbleweed kernel package is installed. The idea of Tumbleweed repo is to collate the latest stable FOSS updates, removing packages to seperate repos to suit users of proprietary drivers, inconveniences the many who want to try newer kernels (and if they use proprietary graphics re-build the module). There is absolutely no need to split out the kernel packages. -- openSUSE Feature: https://features.opensuse.org/311446
participants (1)
-
fate_noreply＠suse.de