Export bzl_library with package files

[duarten]

This allows consumers of rules_pkg to generate docs using stardoc. An example is how skylib does it.

[aiuto]

I have a change ready to send as a PR which will provide sources for running stardoc against.
It is blocked behind the backlog of functional changes.
Still, I don't encourage people to use startdoc themselves. It will always be incomplete documentation because the documentation for common attributes comes form other places.
The docs at https://bazelbuild.github.io/rules_pkg/ will be superior to anything you can build on your own for the forseeable future.

[duarten]

Good to know!

Just to clarify, I'm building docs for rules I'm authoring. It's just that stardoc requires the full transitive set of my deps.

[aiuto]

#567 has a fix. "@rules_pkg//pkg:bzl_srcs" should be usable as a bzl_library.
If anyone wants to patch that in and give it a try that will be great. Otherwise I'll wait until Friday and merge it anyway.
@guw

[duarten]

Works perfectly! I still had to add

"@rules_pkg//:mappings.bzl",
"@rules_pkg//:pkg.bzl",
"@rules_pkg//pkg:bzl_srcs",

as dependencies to my bzl_library.

[aiuto]

Thanks. That is strange. Why :mappings.bzl? That is not actually used by anything. It is just a forwarder. Same for pkg.bzl? Do you use those instead of //pkg:mappings.bzl and //pkg:tar.bzl? They are going away sometime this quarter. #562

…

On Wed, Apr 6, 2022 at 2:12 PM Duarte Nunes ***@***.***> wrote: Works perfectly! I still had to add ***@***.***_pkg//:mappings.bzl", ***@***.***_pkg//:pkg.bzl", ***@***.***_pkg//pkg:bzl_srcs", as dependencies to my bzl_library. — Reply to this email directly, view it on GitHub <#564 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXHHHGZZUFM2SQTFZTMECLVDXHZ7ANCNFSM5SHSE5YQ> . You are receiving this because you commented.Message ID: ***@***.***>

[duarten]

Ah! Thanks, I was indeed using those instead of the pkg:* variants.

[duarten]

Closing as this is fixed in 0.7.0.