-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Ability to manipulate mtrees #191
Comments
hey @thesayyn! I would like to hear more of your expectations or requirements. One of the behaviours I've mulled on, which sounds similar, would be to union more than one mtree hierarchy (i.e. generating a hierarchy per layer on a container image, and then produce a single hierarchy of what the resulting filesystem ought to appear as). Might this be what you're calling hierarchy flattening? |
Great to hear!!!! What I mean by flattening is that given this mtree,
I was imagining we could implement something like
There are multiple variants of manipulations like this I want but can't think of all of them yet! It would even better to implement a generic solution using some combination of https://github.com/google/cel-go with something else to implement a generic manipulation command. |
Maybe I could make a draft PR just to see what it might look like. |
that would be welcome. Since it would be a first for this cli, it would seem easy to either over or under design that experience. Better to just iterate on it. |
Awesome. I just made a prefactor PR that prepares the cli surface for subcommands. |
Hey @vbatts, thank you for the great tool for the great mtree format.
I am a maintainer of the bsdtar toolchain for bazel in https://github.com/aspect-build/bazel-lib/blob/main/docs/tar.md. We are in a need of a commandline tool that understands mtree and can transform them.
Would you be warm to the idea of having a subcommand gomtree that can perform general tasks like path rewriting, hierarchy flattening etc?
We'd like to contribute this feature.
The text was updated successfully, but these errors were encountered: