[opensuse-factory] Introducing linux-tools
![](https://seccdn.libravatar.org/avatar/764c965aec778ca830c3c46e8961926f.jpg?s=120&d=mm&r=g)
I would like to introduce linux-tools into Factory. Some tools are now provided by the mainline kernel, including but not limited to : - cpupower - usbip - perf (already build in kernel sources) That means these packages have to get dropped from factory to get replaced with kernel build-in versions. So, as Tony asked me to discuss it on the mailinglist (what I better should had make in a first place), I would like to know if there is any objection. Regards. Benjamin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/aebdf31d465b04113cd13a6bffde8527.jpg?s=120&d=mm&r=g)
On 01/11/2016, 08:09 PM, Benjamin Denisart wrote:
I would like to introduce linux-tools into Factory. Some tools are now provided by the mainline kernel, including but not limited to : - cpupower - usbip - perf (already build in kernel sources)
That means these packages have to get dropped from factory to get replaced with kernel build-in versions. So, as Tony asked me to discuss it on the mailinglist (what I better should had make in a first place), I would like to know if there is any objection.
IUC, you would use kernel-source and multiple %package rpm directives to generate those, right? If so: +1; -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/d264f2f9a84d894eacb865247778bf39.jpg?s=120&d=mm&r=g)
On pondělí 11. ledna 2016 20:09:14 CET Benjamin Denisart wrote:
I would like to introduce linux-tools into Factory. Some tools are now provided by the mainline kernel, including but not limited to : - cpupower - usbip - perf (already build in kernel sources)
That means these packages have to get dropped from factory to get replaced with kernel build-in versions. So, as Tony asked me to discuss it on the mailinglist (what I better should had make in a first place), I would like to know if there is any objection.
Regards. Benjamin
Hi first let me thank you for doing so, it is great that someone did this, as already mentioned, since this package provides perf, usbip and cpupower, those standalone packages need to be removed from Factory/Tumbleweed. Additional benefit of having this package in Factory is availability of tmon and cgroup_event_listener. It would be great if maintainers of packages supposed to be replaced reviewed devel:tools/linux-tools and shared their opinion/comments/suggestions. Also currently package resides in devel:tools, but perhaps it might make more sense to move it to Base:System. Cheers Martin Pluskal
![](https://seccdn.libravatar.org/avatar/764c965aec778ca830c3c46e8961926f.jpg?s=120&d=mm&r=g)
@jsably : yes, it provides multiple RPMs, as a drop-in replacement ( the exact same rpm names). @martin : yep, indeed, Base:System might be more appropriate. Regards. Benjamin 2016-01-12 9:57 GMT+01:00 Martin Pluskal <martin@pluskal.org>:
On pondělí 11. ledna 2016 20:09:14 CET Benjamin Denisart wrote:
I would like to introduce linux-tools into Factory. Some tools are now provided by the mainline kernel, including but not limited to : - cpupower - usbip - perf (already build in kernel sources)
That means these packages have to get dropped from factory to get replaced with kernel build-in versions. So, as Tony asked me to discuss it on the mailinglist (what I better should had make in a first place), I would like to know if there is any objection.
Regards. Benjamin
Hi
first let me thank you for doing so, it is great that someone did this, as already mentioned, since this package provides perf, usbip and cpupower, those standalone packages need to be removed from Factory/Tumbleweed. Additional benefit of having this package in Factory is availability of tmon and cgroup_event_listener.
It would be great if maintainers of packages supposed to be replaced reviewed devel:tools/linux-tools and shared their opinion/comments/suggestions.
Also currently package resides in devel:tools, but perhaps it might make more sense to move it to Base:System.
Cheers
Martin Pluskal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/bb5f0ecbeb4f5d5ad9bee1e82f4436b4.jpg?s=120&d=mm&r=g)
On 01/12/2016 12:57 AM, Martin Pluskal wrote:
On pondělí 11. ledna 2016 20:09:14 CET Benjamin Denisart wrote:
I would like to introduce linux-tools into Factory. Some tools are now provided by the mainline kernel, including but not limited to : - cpupower - usbip - perf (already build in kernel sources)
That means these packages have to get dropped from factory to get replaced with kernel build-in versions. So, as Tony asked me to discuss it on the mailinglist (what I better should had make in a first place), I would like to know if there is any objection.
Regards. Benjamin
Hi
first let me thank you for doing so, it is great that someone did this, as already mentioned, since this package provides perf, usbip and cpupower, those standalone packages need to be removed from Factory/Tumbleweed. Additional benefit of having this package in Factory is availability of tmon and cgroup_event_listener.
It would be great if maintainers of packages supposed to be replaced reviewed devel:tools/linux-tools and shared their opinion/comments/suggestions.
Also currently package resides in devel:tools, but perhaps it might make more sense to move it to Base:System.
As noted. perf is already built from kernel sources. I would like it to continue to be maintained as it's own separate package. So it's NAK from me to moving it into linux-tools. Also, be aware that there are packing issues here. For example, changes that occur in the kernel-source tree for one of these packages require an updated release of the userspace package but there is no mechanism to signal this. For SLES at least I carry patches directly in the perf package specifically for this but this has it's own issues. Long term, for the perf package, I was considering building it out of the kernel build itself. Again, I don't want the perf package moved into linux-tools. Tony -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/bb5f0ecbeb4f5d5ad9bee1e82f4436b4.jpg?s=120&d=mm&r=g)
On 01/12/2016 10:47 AM, Tony Jones wrote:
On 01/12/2016 12:57 AM, Martin Pluskal wrote: For example,changes that occur in the kernel-source tree for one of these packages require an updated release of the userspace package
I was specifically referring here to changes we pull into the kernel tree from stable updates. A stable update will result in a new kernel version but nothing will auto trigger a package update if the stable changes so requires. We have had perf userspace changes come into the tree via stable. Not often but it does happen. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Benjamin Denisart
-
Jiri Slaby
-
Martin Pluskal
-
Tony Jones