Classic confinement for rust-bindgen

store-requests
1

Hi there,

I would like to request the classic confinement for rust-bindgen Snap. It’s a Rust-related build tool that needs unrestricted file access to system development files (mainly C/C++ headers).

Thanks!

3 Likes
2

Hi @liushuyu ,

The link you provided is not working, can you please elaborate more on what the snap does, and what kind of error you’re facing while confining the snap in strict env? Also for “classic” you need to make sure your snap lands in one of the supported categories here

thanks

3

Ping @liushuyu - this request cannot proceed without your response.

4

@liushuyu as stated above, this request is still waiting on input from you - can you please respond, otherwise we will close it on our side after another 7 days of inactivity. Thanks.

5

This is now addressed. rust-bindgen is set to “public” now. Previously, there was an issue with the Launchpad builder, but it seems to have been fixed recently.

6

Hello @liushuyu , just to clarify, your request for classic is no longer required, right?

7

I’m sorry, but the request for classic is still required because the system needs to read C/C++ development files.

8

Hey @liushuyu

So rust-bindgen automatically generates Rust FFI bindings to C (and some C++) libraries. Thus, it clearly needs access to the development files (mainly C/C++ headers).

However, rust-bindgen does not seems to fit very well in any of the supported categories for classic. I wonder if access to the required files via system-files (/var/lib/snapd/hostfs/usr/include ) would be more appropriate for this requirement

9

Hmm rust-bindgen feels like a compiler to me… and so would fit in that supported category, right?

10

The issue here is, aside from /usr/include, it might also need to access other locations if the user specified extra include paths (just like clang or GCC). The path might be inside /usr/lib(where we put cross-compilers) if some compile builtin headers are used.

I think rust-bindgen could be classified as a compiler, except it ingests C/C++ sources and outputs Rust source files instead of assembly or binary.

11

A compiler takes inputs and produces outputs - which is what rust-bindgen does.

Also it needs access to system installed headers etc, very much like a traditional C/C++ compiler. So I still think this fits quite clearly into this category. As such, the requirements for classic confinement are understood. I have vetted the publisher. This is now live.

1 Like
12

Hi there,

I can see the ppc64el and s390x builds are still in the “pending review” state while the other builds are approved for release. Is this expected?

13

Apologies, they need to be queued manually and it appears I forgot to do these last two. Done.

1 Like