Jon Johnson

Okay wolfi now has this: ``` curl -sL https://packages.wolfi.dev/os/withdrawn-packages.txt | wc -l 637 ``` We should be able to key off that for deleted packages.

> I would prefer not encouraging registries to do more (potentially unnecessary) work on any of the APIs in the "pull" workflow. Some clients will need this information, but (IMO)...

> The question that remains on my side is why apko does not preserve ownership If I had to guess, it's not deliberate, just an oversight. Since `apko` has the...

> I think probably the correct solution is to add something like a WorkspaceDirFS field to the Build class/structure, which points to the original MemFS data structure if RetrieveWorkspace() fills...

This isn't currently supported, but it wouldn't be impossible to implement... just a matter of priorities 😄

Doesn't fail for me on macos :/

I need to parse through this more carefully to see if I'm missing an easy place to fix this, but part of the difficulty here is that everything in `glibc.yaml`...

> One doesn't need to order (all runtime deps) + (all build time deps). only only needs to order (build time deps) versus older ones. This is tricky because if...

> You build them in circle until steady state is met and no new packages are getting produced. This sounds fun, I'm not sure how we'd go about implementing this...

https://github.com/wolfi-dev/os/pull/41342 is the kind of thing where _if_ we can do multi-hop ordering then testing changes is much nicer, but because it's basically impossible to do at the global level,...