The immediate issue here is the deployment issue with Rust applications:

[dependencies]
dbus = "0.3.4"
gtk = { version = "0.1.0", features = ["v3_16"] }
gdk = { version = "0.5.0" }
quickersort = "2.0.1"

We can't really permit fetches of third party modules. Do we know if the distributed tarball (if it exists) contains these in the tree?

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

That does present a security risk I'm not entirely comfortable with :/ Ideas?

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.

Thanks, much apprecicated

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.

It is possible to update the dependencies within the cargo.toml file for the project to be changed from pulling from crates.io to point to the git url (i.e github) or even a local path as well. Would this be a possibility to alleviate your concern, or should I continue to look further?

The following contains the dependency tree for this app:

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

I am sorry if I am lacking in understanding when it comes the packaging for Solus, as I have not done so yet.

I would definitely like to figure out how to package rust applications for Solus, as I am someone who is working on some rust applications in my free time.

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.

I'm not sure you got the memo saying Don't reopen issues. It was literally the first thing I stated. Leave this to the triage team.

I also vote for inclusion of this app. It'd be nice to have a user-friendly app to configure systemd services :)