On Fri, Jun 11, 2021 at 06:27:19AM +0200, Fabio M. Di Nitto wrote:
> Hey everyone,
> 
> I have been reading the current guideline here:
> 
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/
> 
> and for the most it´s pretty clear when packaging a standalone crate
> / rust generated binaries (given this is my very first step into
> understanding rust).
> 
> I am currently facing a slightly different challenge as my upstream
> project, a bunch of C shared libraries (also available in Fedora),
> will soon grow rust bindings.
> 
> The rust code will be part of the normal upstream tarball / etc.
> that will include at that point a mix of different languages.

I maintain two such projects with Rust bindings
(https://src.fedoraproject.org/rpms/libguestfs
https://src.fedoraproject.org/rpms/nbdkit).  We don't package the
bindings in Fedora, but instead distribute the source separately
(eg. https://lib.rs/crates/nbdkit)

Other programs that use the bindings bundle them.

It's not ideal at all, but it was the path of least resistance given
the way Rust stuff is built.

> The upstream build system already takes care to call into cargo for
> example and I am wondering how the current rust rpm macros are going
> to work with it (or viceversa).
> 
> Does anyone have experience in packaging mixed sources?
> Could you share your spec file please (or just the srpm name ;))

For an example of very very mixed sources, see the libguestfs link
above, although it won't help for Rust or Golang.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
_______________________________________________
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to