Classic confinement request for dcrup

store-requests classic-confinement
1

name: dcrup description: A Cargo-like build tool for C/C++ projects written in Rust. snapcraft: https://github.com/dexoron/dcr/blob/master/snap/snapcraft.yaml upstream: GitHub - dexoron/dcr: DCR is a utility for managing C/C++ projects in a Cargo-like style. · GitHub upstream-relation: I am the main author and maintainer of the project. supported-category: compilers

reasoning: dcr is a developer tool designed to orchestrate C/C++ builds. It cannot function under strict confinement because it requires:

  1. Dynamic invocation of arbitrary system compilers, linkers, and build tools (like gcc, clang, make) installed on the host system, which are outside the strict sandbox.
  2. Full read access to system headers and libraries (e.g., /usr/include, /usr/lib) to compile and link projects correctly.
  3. Arbitrary filesystem access to read source code and write build artifacts in any directory where a user decides to run the tool.

I understand that strict confinement is generally preferred over classic. I’ve tried the existing interfaces to make the snap to work under strict confinement.

2

This request has been added to the queue for review by the @reviewers team.

3

Hi @Dexoron ,

Thank you for raising the forum request.

While I agree with the technical aspect of why the snap needs classic permissions, please note that classic confinement is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. As of today, I believe that dcrup doesn’t meet this criteria because of the following reasons:

  • The project seems to be very fresh, according to the upstream repository.
  • The projects seems to have little community around according to upstream repository (contributors, issues, PRs, etc.)
  • I could not find evidences that the project has a strong enough user base currently.

Thus, considering these factors, I think dcrup should not get classic confinement as of now.

1 Like
4

Yes, my project is new. The first release was on February 11 of this year. But I’m actively developing it. This is a long-term project for me, and I don’t plan on giving it up; the audience is growing all the time, and I already have one maintainer.

Could you tell me what requirements I need to meet to be included in “classic”?

5

Hi @Dexoron,

We are still in the process of formalizing the exact requirements and fleshing out the details for the “classic” track.

We want to ensure the criteria are fair and sustainable for the community, so we are taking the time to map them out properly.

We will share the official criteria as soon as they are ready.

Keep up the good work and you are welcome to submit a new request for classic in the future.

Thanks!

1 Like