Hi everyone,

I've been using sccache [1] as wrapping compiler cacher, not unlike `ccache`, but with more storage backend options, and at least the option to do what `distcc` has classically been used for, but with auto-distribution of toolchains (!). It's what mozilla uses for their software builds, and supports C, C++, and Rust.

Now, to make my life easier and to get the ick out of installing sccache, I'd like to package that as Fedora package. As far as license is concerned, I think that should be fine – it's Apache-2.0-licensed.

Thing that I'm not clear about is how to approach packaging software like that 
for Fedora:

- It's rust, and cargo pulls down a host of dependencies for the build.
 - No idea how make it use things as packaged by fedora when available, and how to make a license SBOM for the rest.  - the spec generated by rust2rpm doesn't tell me much; an rpmbuild of the result lists about 100 missing dependencies of the kind "crate(base64/default)" - it exists in different "configurations" (with the distributed compilation agent, and without)

It seems to be a solvable problem; debian testing does ship the current release.

Now, I'm not a Rust dev, but I'll happy to do the RPM, care about updates, sort the occasional bug, etc. But putting me as sole maintainer would probably be a misjudgement of my own capabilities.

Would someone want to share this burden with me?

Best regards,
Marcus

[1] https://github.com/mozilla/sccache

--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to