Christian Duerr

> Hmm, using Ruleset::new(ABI) would solve this potential issue (not only with FS access rights but also future access types). I don't think passing ABI to `Ruleset::new` would be a...

> Which kind of applications and use cases do you have in mind? I was just playing around with the idea to print warnings if sandboxing wasn't supported or if...

I just saw that `ABI` already has a `new_current` function that is used internally. If that was made public, that would be sufficient to implement this. Alternatively if we wanted...

I just feel like it would be better to provide a predictable way to retrieve this in the landlock crate, rather than people inevitably trying to satisfy the requirement for...

How do you envision this to be done? Our lockfile analysis cannot run arbitrary commands. While we could use this for lockfile generation, I don't see us being able to...

Yeah I apologize I must have been completely blind when reading this yesterday. It states clearly multiple times that this refers to lockfile generation, so not sure why I thought...

I'm not sure if a `--wide` option is the best solution here. we already have alternative output options which show the full project name (`--json`), but I'd imagine the goal...

Is CLI the right place for this? Since the CLI basically just prints what the API responds here, it seems like this might be better handled on the API side?

> The API is returning status as Incomplete, but we show no indication of that. If this were a package that was still being processed, the CLI should probably print...

Since submission is now done automatically for packages that did not exist yet, this will show the following message: ``` ⚠️ Thank you for submitting this package. Please check back...