Ettore Di Giacinto

compilationspec would clash and be a bit confusing with the current `CompilationSpec` struct, what about `inline` or `inline_oci` or `oci_steps` ?

We already have the `uninstall` keyword in the finalizer, but since we don't save those in the system database, it is a no-op as for now

That's awesome and looking great! Thanks you so much! care to open up a PR to see if it's passing tests?

The issue is about expanding the docs in https://luet-lab.github.io/docs/docs/concepts/packages/#package-provides with a pratical example

mmm I don't see the layer/ghc under `packages`? https://github.com/mocaccinoOS/community-repository/blob/main/packages/apps/collection.yaml I see it in the anchors, but not sure if it gets built at all?

this looks likely something to do with the versioning. I've tried locally with a simple package in two repos, one at `0.8.4` and the additional repo the same package, but...

@geaaru Can we close this issue? or is this still valid?

Client implementations are in: https://github.com/mudler/luet/tree/master/pkg/installer/client

Maybe a good time to have a look at #90 - this for sure is not coming directly from luet code, as we don't handle explictly file copy or unpack....

Thanks for the detailed reporting, this indeed is a regression introduced with the values files feature. `luet tree images` is unaware of any values file.