[opensuse-factory] Kernel:Tools project
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm thinking about creating Kernel:Tools project to maintain packages like this: sparse trinity mmtests systemtap trace-cmd xfstests ksplice in the future module-init-tools and friends (or maybe not, if it would cause dependency problems in Base:System) Ideas, comments? thanks, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQs8VGAAoJEL0lsQQGtHBJ/g8P/2hJrvpZBl0AENPlAmYMT2pO JcAbdQuofuemRczqZA7XXhY7cXEIbrmvoAyJNfaHV19sMT26Gh3CfiWiy7g4fgn5 xFuZ6Pv8G/oFpEa6i6ZDXDBN1/Ype6Nvuiv/y1iFa3mtPCdrlvr1zfP/3s/qISzU lR9T0vTPiQaH2a8t+QzNS/2QYL9vTbLafb/0pti4DYOvCJ3ZXQ/sgXdUehGBmlBH TxpkhEqgYY1wmO8CW0LUmLaeOpZlVDnBb/F7/3hzIFfKoJ81jdjxLvUalmJIiQWc 7ZIGJDXV6mxksR/lcF4SOyOh/DQ+R9MGLHNs8rKsfyisCkuxboV8LBoqSi3qHDjl XUd4xy1qbcISPaC9cYxlsJl8lwxNqxjekeyh693UCoGhZHUK6kCYt+P/likrqjli ++dJ3hjSCKP5juG/8NrkZ/O3LIieWNbR2m4nY/+7xmLq37yAmp04HFV1Gw5RqDUx C6misGUklk8hR0xk7o2Hfgz/V7GfK/bXZNNagdrSZEfI+z2YHDU2jQGT/bfoBkbe FQdX87SrteasumLFK5CAGmOBQ34h5aFsnuCC0dKdsXhXqH0hNv2odmwSigFSI9h4 glevVmGZ6IfGc2ijHHesxxGcrS/8VxH85UNlRjQ185Eu4f9fRHLa0WDCkVdI8YYc uM9F3qevaFlYNF/vH9n2 =k80B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2012-11-26 20:38, Jiri Slaby wrote:
I'm thinking about creating Kernel:Tools project to maintain packages like this: sparse
Put that in devel:tools, because it really goes beyond the kernel.
trinity mmtests
undecided.
systemtap trace-cmd
devel:tools, maybe? strace is in d:t, I note.
xfstests
filesystems is a good association, IMO. It should stay there.
module-init-tools and friends (or maybe not, if it would cause dependency problems in Base:System)
undecided
Ideas, comments?
"What, _another_ develprj?" There are other packages from Base:System that (I think) would fit better elsewhere (e.g. bluez* to hardware), so as to unclutter Base:System, if the unorganized nature of Base:System is a concern. For the few that I called "undecided" above, a separate dp does not seem justified just yet. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/27/2012 12:38 AM, Jan Engelhardt wrote:
"What, _another_ develprj?"
There are other packages from Base:System that (I think) would fit better elsewhere (e.g. bluez* to hardware), so as to unclutter Base:System, if the unorganized nature of Base:System is a concern.
More or less yes. Many packages are not Base:System at all. Like sparse.
For the few that I called "undecided" above, a separate dp does not seem justified just yet.
devel:tools fits the best, I think. (Given we will leave module tools where they are.) So I did a first submit rq of trinity from my home to devel:tools. thanks, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQtJ5OAAoJEL0lsQQGtHBJ2ksP/19R1Pe7JJ1w/fNbTtoB1l21 835Mkdcw8Ojmf6QSw/Lq+VinZS5t4JsMtEftHqmQFfrWlv8E/cH+reldM0JAxDbd RUMwj5lFYQxKHR51nPOuErjGK0S17NrnpkY1rIRxXu2iPcZV3FrkG3LuYZX6Ia0t sg2EUJ4zzDlvGy2bbuGgRdcGMsm24qawFMWAPem82JHkZW34WzBU7S6p/FwnlwgP uYa+KSXufsoP71bx5vizp/w3knP68AKGarOYBWeaxa6ezEnej259E1YNc07yWgam YS+GDdpESwjCMNQXwd7VV5X+nkh2q+KizVi7CEfzP5aJYi5+x4gyvCFgAITkY2Ht aIFVOAjIMQGKv/cbm2VBv1Ylloxg9Vhlik335yTVt7/Ax3qvzn9jMnJ7EF826RXJ juyO1GfdjEqwtGfI8W8Cyktr8VcbuJ4hhCt3kdi3yaLShVCGnMhk0IgAFkE1SXUo O5Je34OOHX9oFdJg6oU93UPcJY7alIgnb1+ouVry8dnoYkdwhMmfdtVENKCcAI8B YAQAfJuYSVsBYWkNA5W6UOqMzGIf+g1kg+BHc7DpTzzKGk0MfpU+kEMWgmhFnDMy 81b29KC7yNPA8XfNvxo56RBTh0YQRSbX4IhmVrj2hKaZRDmH/YPniln0wgW4SPRs Gpf98BPehDa0+DgsOR0l =6X4i -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2012-11-26 at 20:38 +0100, Jiri Slaby wrote:
Hi,
I'm thinking about creating Kernel:Tools project to maintain packages like this: sparse trinity mmtests
If this goes ahead I have a package already for mmtests in my home project that I could start maintaining properly. I did not try and make it part of any project as I was not sure what a good fit would it be. The primary use case I had in mind for it was collecting data from a running kernel but there is also the benchmark projects and it could be argued that benchmark would be a better fit.
systemtap trace-cmd
trace-cmd is already in devel:tools. It could be moved I guess as kernel:tools might be a better fit. I've no opinions on the rest.
xfstests ksplice in the future module-init-tools and friends (or maybe not, if it would cause dependency problems in Base:System)
Ideas, comments?
thanks,
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/27/2012 01:01 PM, Mel Gorman wrote:
On Mon, 2012-11-26 at 20:38 +0100, Jiri Slaby wrote:
I'm thinking about creating Kernel:Tools project to maintain packages like this: sparse trinity mmtests
If this goes ahead I have a package already for mmtests in my home project that I could start maintaining properly. I did not try and make it part of any project as I was not sure what a good fit would it be. The primary use case I had in mind for it was collecting data from a running kernel but there is also the benchmark projects and it could be argued that benchmark would be a better fit.
So it looks like I won't push Kernel:Tools forwards and will stick to devel:tools only. sparse and trinity are there by now. Anyway, mmtests would be good to have there too, I think. -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Nov 30, 2012 at 02:11:03PM +0100, Jiri Slaby wrote:
On 11/27/2012 01:01 PM, Mel Gorman wrote:
On Mon, 2012-11-26 at 20:38 +0100, Jiri Slaby wrote:
I'm thinking about creating Kernel:Tools project to maintain packages like this: sparse trinity mmtests
If this goes ahead I have a package already for mmtests in my home project that I could start maintaining properly. I did not try and make it part of any project as I was not sure what a good fit would it be. The primary use case I had in mind for it was collecting data from a running kernel but there is also the benchmark projects and it could be argued that benchmark would be a better fit.
So it looks like I won't push Kernel:Tools forwards and will stick to devel:tools only. sparse and trinity are there by now. Anyway, mmtests would be good to have there too, I think.
Ok. It's not something I can do this week due to other commitments but I've added a TODO item to update it to 0.08 and punt it towards devel:tools for review. Thanks. -- Mel Gorman SUSE Labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Jan Engelhardt -
Jiri Slaby -
Mel Gorman