You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rules_pkg package is pretty good at expressing a directory structure to be created in an archive etc., with its PackageFilesInfo and PackageFilegroupInfo providers. mtree files are similar: they also express a directory structure, except it's not known yet at analysis time.
rules_pkg could integrate nicely with the aspect_bazel_libtar if an mtree spec could be created from targets with PackageFilesInfo or PackageFilegroupInfo. The current approach, where you'd have to mutate an mtree spec with awk or some other tool to match the package structure, is cumbersome by comparison.
Maybe as a second step, support for PackageFilesInfo/PackageFilegroupInfo could be directly added to the tar rule as well, so that the user doesn't need to separately keep the archive inputs as a flat list of files.
The text was updated successfully, but these errors were encountered:
The
rules_pkg
package is pretty good at expressing a directory structure to be created in an archive etc., with itsPackageFilesInfo
andPackageFilegroupInfo
providers.mtree
files are similar: they also express a directory structure, except it's not known yet at analysis time.rules_pkg
could integrate nicely with theaspect_bazel_lib
tar
if anmtree
spec could be created from targets withPackageFilesInfo
orPackageFilegroupInfo
. The current approach, where you'd have to mutate anmtree
spec withawk
or some other tool to match the package structure, is cumbersome by comparison.Maybe as a second step, support for
PackageFilesInfo
/PackageFilegroupInfo
could be directly added to thetar
rule as well, so that the user doesn't need to separately keep the archive inputs as a flat list of files.The text was updated successfully, but these errors were encountered: