Package Base Details: bcc-git

Git Clone URL: (read-only, click to copy)
Submitter: mmlb
Maintainer: edh
Last Packager: edh
Votes: 7
Popularity: 0.000611
First Submitted: 2015-09-29 15:09 (UTC)
Last Updated: 2022-03-30 14:41 (UTC)

Latest Comments

1 2 Next › Last »

edh commented on 2019-10-13 10:23 (UTC)

@emanuele-f The C bindings should work just fine in the bcc package. Hence, it is separate from python-bcc.

I agree that not having the tools in the PATH is kind of awkward but there are a number of names which would clash with standard Linux tools. Defining a sensible ordering in the PATH IMHO does not make sense and hence I just stick to what upstream has decided to do.

emanuele-f commented on 2019-10-13 09:58 (UTC)

Why python-bcc-git is optional? Tools will fail with "No module named 'bcc'" if that is not installed. It would also be useful to have the tools in the PATH, I had to check the .pkg.tar.gz contents to locate where the tools are installed.

osandov commented on 2019-08-28 19:02 (UTC)

The provides/conflicts directives should be fixed now. Let me know if anyone runs into issues.

gamanakis commented on 2019-08-28 03:21 (UTC)

Please fix the "provides" directive. Instead of bcc-git it should say bcc, otherwise other packages depending on bcc are broken (e.g. bpftrace).

iamazat commented on 2019-05-11 13:32 (UTC)

Maybe this package should provides bcc?

renyuneyun commented on 2018-07-10 08:47 (UTC)

There is a file clash with postfix because of /usr/share/man/man8/trace.8.gz . Probably this should be handled... (Though I can uninstall postfix for me case.)

edh commented on 2018-02-16 08:29 (UTC)

Thanks for the note. That was just a plain mistake, I indeed meant to direct the message at @osandov.

mmlb commented on 2018-02-16 02:25 (UTC)

Hey @edh I'm not the maintainer anymore, you want @osandov.

edh commented on 2018-02-15 23:26 (UTC) (edited on 2018-02-25 21:50 (UTC) by edh)

@osandov I recently adopted the non-git package and overhauled the PKGBUILD. Feel free to move over everything that seems fitting. Besides cosmetic and slight variable value changes at the very least the checkdepends should be updated.

Btw. since I already maintain one version of the package I would not mind to keep track of one additional PKGBUILD file. Hence if you are not really interested in maintaining it and simply stepped up due to some imminent need, I would be more than willing to take ownership of this package as well.

EDIT: Remove nonsense about man pages and redirect message to username osandov.

Gioconda commented on 2018-01-29 07:31 (UTC)

Hi, the buildscript have some errors. First, the provides array would be 'bcc', not 'bcc-git', about libbcc-git, the same, would be 'libbcc', and maybe will be needed to add to conflicts array too. For more information check ( Furthermore, according to the arch user repository guidelines to share package builds, you need to put your info as maintainer in the first lines(