Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)
On Thu, Dec 01, 2016 at 06:24:56PM +0530, Ritesh Raj Sarraf wrote:
> 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.
That sounds like a good solution to me.
Regards,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: