Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2016-11-30 at 22:40 +0100, Christian Seiler wrote: > > many thanks for the explanation, so from a technical point of > > view there is no package naming conflict, although it is somewhat > > counter-intuitive to end up with a source-package "bcc" and a > > binary-package "bcc" where the latter isn't built from the former > > but instead contains a completely different application. > > Maybe the new source package could be named bpf-bcc? That way there > would be no confusion with respect to bin:bcc vs. src:bcc, and the > source package name is still quite short, yet descriptive. Just a > suggestion. How about ? src: bpfcc bin: bpfcc-tools, libbpfcc, libbpfcc-dev, bpfcc-lua, python-bpfcc This relates well to what the tool is: BPF Compiler Collection, both in src and binary names. I think I'll stick with this name unless there are concerns. Thanks. - -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlhAHaAACgkQpjpYo/Lh dWnMqg/+JGft9tC0/Pmvi4dAWeBw1dXHf86+8U06LDe05N+PS6c3ery6WsmMKdEM Nav7tcqjCBHESHHm1PrifWU8CSJqizwoPStD8jsBF7woRbD/FPIE2+N4ZCXI1mBq doSwMcuZt/LfFhKR/lwmptl1HS2FfNDr/pJCGd0D7ZVtaUSqEFES5vDwx5YE5S9E MyeYmW56hxEmcb5ASIjHHqGnTAG7wd1tKoQn2w7tcTAbdfSBgU53jlSekiy/b7fC y3o8EzUCjQBnrCQGPXN1/0jpaqrf5e4wq8ETpttV25P+dZNAa4jtf7SuHRcZnMDg UfzmTl45YxZVbOKWAX6UykYMgyUUSzYC1aQPGRyY1M9dgruAWRUTK0OzBaYmgAkv 9UDDaNPtMOLFR6YW3ZndH0qfkZIl6q0+WJVqDBBBmsPPZFRd9ilVyXv0UQffl2c3 9Etwh48wp/aFFnyG1IOqteuE688Y9CFTO6cVxHbkXRQx4C4xWZ4vjxGQC/r0j4Ne OFGk4zjFdMdfeNYGMfofe6IyUy6YhbCQavj25sXGM/ed2P0V8yWMnaMjnX94+L6m UL8102MZS2ei3FF/lyrubD0Up59rQCeNygJDqM9gXDT44PUY829qXaJqeNlstsAK 6mkvMyDiMj1A5rZnrY7Ge9i6RWibFvqiUssFixE0ToNwKExC6ZE= =9yGo -END PGP SIGNATURE-
Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)
On Thu, 2016-12-01 at 00:56 +0530, Ritesh Raj Sarraf wrote: > Hello Karsten, > > On Wed, 2016-11-30 at 20:05 +0100, Karsten Merker wrote: > > Hello, > > > > bcc is a package (and executable) name that is already in use for > > another program in Debian. From https://packages.debian.org/sid/bcc: > > I'm aware of it. bcc is an already packaged binary package. It build from > source package: linux86 > > For this package, I've tried to be close to what upstream has already named. > So, for Debian, only the source package name is: bcc. [...] Please don't do this. When the same name is used for a binary package and for a source package that doesn't build that binary, it tends to result in mis-assigned bugs as BTS users don't consistently specify which they mean. Ben. -- Ben Hutchings A free society is one where it is safe to be unpopular. - Adlai Stevenson signature.asc Description: This is a digitally signed message part
Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)
On 11/30/2016 10:32 PM, Karsten Merker wrote: > On Thu, Dec 01, 2016 at 12:56:14AM +0530, Ritesh Raj Sarraf wrote: >> On Wed, 2016-11-30 at 20:05 +0100, Karsten Merker wrote: >>> bcc is a package (and executable) name that is already in use for >>> another program in Debian. From https://packages.debian.org/sid/bcc: >> >> I'm aware of it. bcc is an already packaged binary package. It >> build from source package: linux86 >> >> For this package, I've tried to be close to what upstream has already named. >> So, for Debian, only the source package name is: bcc. >> The binary packages are: >> >> rrs@learner:~/rrs-home/Community/Packaging/bcc (master)$ grep Package: >> debian/control >> Package: libbcc >> Package: libbcc-dev >> Package: python-bcc >> Package: bcc-tools >> Package: bcc-lua >> 2016-12-01 / 00:52:49 ♒♒♒ ☺ >> >> Does it make sense ? >> >> If you have suggestions, please mention them, because it'll be >> easier to make the name changes now. > > many thanks for the explanation, so from a technical point of > view there is no package naming conflict, although it is somewhat > counter-intuitive to end up with a source-package "bcc" and a > binary-package "bcc" where the latter isn't built from the former > but instead contains a completely different application. Maybe the new source package could be named bpf-bcc? That way there would be no confusion with respect to bin:bcc vs. src:bcc, and the source package name is still quite short, yet descriptive. Just a suggestion. Regards, Christian
Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Karsten, On Wed, 2016-11-30 at 20:05 +0100, Karsten Merker wrote: > Hello, > > bcc is a package (and executable) name that is already in use for > another program in Debian. From https://packages.debian.org/sid/bcc: I'm aware of it. bcc is an already packaged binary package. It build from source package: linux86 For this package, I've tried to be close to what upstream has already named. So, for Debian, only the source package name is: bcc. The binary packages are: rrs@learner:~/rrs-home/Community/Packaging/bcc (master)$ grep Package: debian/control Package: libbcc Package: libbcc-dev Package: python-bcc Package: bcc-tools Package: bcc-lua 2016-12-01 / 00:52:49 ♒♒♒ ☺ Does it make sense ? If you have suggestions, please mention them, because it'll be easier to make the name changes now. - -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlg/J9YACgkQpjpYo/Lh dWmy1xAAoVz8XUiAoGzAb8lcGZsIFl0aZlXs+QnWSTny0RfsLkentFH4so3W3dE7 IFGRcv9I1dqtgZulx2QFppQayut92Ph8EfKcttlT62Mm0kMT/jgyGrrM6LAa7HY0 gxOsLtgjgXjnMZe57DAddWyX0HyJX3yElA3Cc3RBl1HM5ZRrXkaGbNVjw+4WPC/p KFGTbmvmvMxb3lITL5p184N0SgSG8ILci/iGD7knFY/uLKNr0Ygx3QJdBzfG94O8 bst3h5eZBRPFxzw9CoQJP4PHwLBSoOU9KX5VeQ2XogTjVHJYI6GZ5rJSvodicoJZ QoeOjkM9fcgLTy3YBEJpM1dGJfiseuOO2dFLPFRUIaMvBzgo/WJBWB2v9xtZQC25 kKLiqpSBrLnZYyrXQtQYFaDs7BGnoix8U/KWdZbifW6WW4Q2z5Jgc/pMrC23/Ecd zDz8pEo1dB4Zt/zfDjtqALr7EUVh1CBDEiMT+eDC49C0HJ4wpssCjMKcrk9KlLKx XyNS7GwmTQetGgrvRto7EuYRyX7JhHaxyKrpdZTZoKLUYPM6dImj68CGtfkq1Cwd 2DCNq338J2jt3RA6Tire83J8BHOT94hkuJ7tQr2MjJ9MjZOZ77IwJxrSH3tW8BEw 8l+JPSXRhBPWuZkGGG4UuYBFLkNrheRLfU1AR/aZ/fhYDEB91Us= =emD/ -END PGP SIGNATURE-
Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)
Package: wnpp Severity: wishlist Owner: Ritesh Raj Sarraf * Package name: bcc Version : 0.2.0 Upstream Author : IO Visor Project (https://github.com/iovisor) * URL : https://github.com/iovisor/bcc * License : Apache 2.0 Programming Lang: C, Python Description : Tools for BPF Compiler Collection (BCC) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more This is a great tool to debug and instrument your kernel and applications. It also is a a performance characterization and analysis tool I have an interest in Debugging and Analysis and I intend to use and maintain it under Debian. As with most of my packages, I intend to maintain it under collab-maint
