Publish [email protected]

[filmil]

Release: https://github.com/filmil/bazel_elfutils/releases/tag/v0.1.1

Automated by Publish to BCR

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (elfutils) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[kotlaja]

Let's maybe use the same name of this module as it is already on github: bazel_elfutils?

[filmil]

Interesting. Could you please point me to a naming convention doc that explains how to choose the module name? Best I have found is https://github.com/bazelbuild/bazel-central-registry/blob/main/docs/bcr-policies.md, which doesn't say anything about this naming convention. Specifically, it makes sense (to me) for the git repo to contain the prefix `bazel_`, because I have other repos too, so that prefix is significant. I can for example fork elfutils and name that fork `elfutils`. But it doesn't specifically make sense for the bazel module to be named `bazel_something`, because everything on BCR is for bazel. I ask because at some point I was asked to strip the `bazel_` prefix from another module name.

…

On Wed, Oct 1, 2025 at 7:10 AM Nevena ***@***.***> wrote: *kotlaja* left a comment (bazelbuild/bazel-central-registry#6059) <#6059 (comment)> Let's maybe use the same name of this module as it is already on github: bazel_elfutils? — Reply to this email directly, view it on GitHub <#6059 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB4GMFSMKHHU7TYXBGWIH33VPOGPAVCNFSM6AAAAACH7ERMRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNJWGUZTOOBSHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[kotlaja]

Regarding naming convention, the most important rules is to have a succinct and unambiguous name. Here I don't have a strong opinion (that's why I phrased it with question mark and maybe) since also elfutils follows this rule. And it makes sense what you're saying regarding bazel_ prefix, so let's go with how it already is. :)

FWIW, I mostly suggested that name due to the cases where users would search in the BCR for the same name as it is in github.