Capsicum support about sysctl-rs HOT 7 OPEN

Can't speak too much to the other points, but I'm happy to aid in maintaining libcasper support in capsicum. I am curious about the benefits of adding libcasper support to capsicum vs creating a libcasper crate that depends on capsicum-rs.

from sysctl-rs.

Well, nobody will ever use libcasper without using capsicum. There are, however, plenty of use cases for capsicum that don't require libcasper. But shorn of its services, libcasper is pretty small. IMHO it doesn't require a standalone crate. What about adding it to capsicum-rs, but gated by a feature flag?

from sysctl-rs.

Thanks! That makes sense.

from sysctl-rs.

Thanks for the suggestion! I like it and it seems you thought about all the questions I would have. Not a fan of the global variable for the casper connection but if it's between that and breaking the API I prefer not breaking the API.

Having it behind an target_os gate and not feature flag seems OK to me (but not for all unix since I don't think macOS/iOS has this right?).

from sysctl-rs.

Correct. Capsicum is FreeBSD only. There was a Linux port, but I don't think it's complete or currently maintained.

from sysctl-rs.

Status update: I've gotten Casper working on a different real-world project (but not cap_sysctl). But I actually no longer have a personal need for cap_sysctl, so I'm going to deprioritize that part. Currently I'm blocked by a few PRs at https://github.com/Inner-Heaven/libnv-rs/ before we can integrate this into the capsicum-rs crate.

from sysctl-rs.

👍 Thanks for working on this and adding an update

from sysctl-rs.