crates.io releases?

[matthiasbeyer]

Hi, there have been five releases of this crate, but none has been published to crates.io yet.

Any chance we're getting a crates.io release soon?

[MatteoNardi]

Hi Matthias. Let's talk about it!

So far we've decided not to publish the pulsar binary on crates.io because a simple cargo install exein-pulsar wouldn't be enough for installing pulsar, hence the installation script, which installs the binary, creates the configuration files and installs the detection rules. In general, pulsar is the kind of program which you install from a package manager and start using systemd rather than the usual rust utilities available on crates.io.

A different thing would be if you wanted to use some pulsar modules as a library, in which case it would make sense to get it from crates.io. Right now your Cargo.toml would have to point from to this github repository, as we're doing in the example.
If you (or anyone else really) want to use our modules like this, let us now! We've gone an extra mile to make it possible for it.

Let us know what you think and about your use-case.

[matthiasbeyer]

Hi! So my usecase would be to use it as a library. I do not yet have anything "production ready", so this is not a time-sensitive thing here, but if I play around with pulsar and what I do turns out to be a good thing to do, it might result in something production ready at some point. And for this, I would need it to be on crates.io, because otherwise I cannot release my code on crates.io (because it forbids git dependencies).

So my usecase really is having a exein-pulsar = "0.5.0" in my Cargo.toml. 😆

For now_ I am fine with a git dependency. But at some point I might be not 😃 .

[MatteoNardi]

We've discussed this internally and decided not to publish on crates.io for now. Here are our concerns:

• We're depending on an unreleased version of aya. We'd have to wait for their next release and we're worried this might repeat in the future, since we like to take advantage of the latest eBPF features when available. This could result in a crates.io release very old compared to our main branch, which would be bad.
• We've not committed to API stability yet and it is not our main concern.
• We don't think complex binary applications like Pulsar should be installed from crates.io, as they require root access and probably some setup.

We will leave the issue open to track interest from the community for this specific feature but we won't be actively tackling it for the time being for the reasons above.