If that is the case would it be possible to have a protobuf3 package instead of upgrading protobuf 2.6.1?

With the recent addition of the [replace] section in the Cargo.toml file to override the path to dependencies to point to a local file, this should make it possible to package for solus. I am currently learning how to package, so I can start building the dependencies for solus.

Is it possible that when packaging this application to do the following:

• include an already built binary by means of cargo build --release by the packager
• include the policykit and desktop files
• and then just require the needed c libraries

The following contains the dependency tree for this app:

After looking into the security aspect of crates.io, it has been discussed a lot at https://github.com/rust-lang/crates.io/issues/75 but nothing has been done yet.

I will look into the security of cargo and crates.io to see what it currently being done in regards to this. If this does not work, I remember reading something about setting up a local repository for dependencies. I will let you know my findings.

There is a tarbell provided, but the makefile is essentially making use of cargo, provided by the rust package already in the repo, to retrieve the rust libraries needed, from crates.io, to work with the C libraries on the system for gtk, gdk and dbus