Change: Crystal Language #3690

Closed
opened 2026-10-01 11:36:20 +00:00 by amoloney · 9 comments
Owner

This proposal introduces official native support for the Crystal programming language compiler (source package crystal-lang, producing binary crystal), its dependency manager (shards), an automated spec generator (cr2rpm), and standard RPM packaging macros (crystal-rpm-macros) into Fedora Linux. Shard libraries will be packaged following the Shard-as-RPM model, enabling offline, secure, and reproducible compilation across the distribution.

Owners, do not implement this work until the FESCo vote has explicitly ended.
When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the FESCo ticket policy and the Changes policy for more information.
If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.

This proposal introduces official native support for the Crystal programming language compiler (source package crystal-lang, producing binary crystal), its dependency manager (shards), an automated spec generator (cr2rpm), and standard RPM packaging macros (crystal-rpm-macros) into Fedora Linux. Shard libraries will be packaged following the Shard-as-RPM model, enabling offline, secure, and reproducible compilation across the distribution. * [Change proposal](https://fedoraproject.org/wiki/Changes/CrystalLanguage) * [Devel Post](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/DRQ7FITOBQDA5L2PSNWUR3JSUZV4NOPX/) * [Discourse Poll](https://discussion.fedoraproject.org/t/f46-change-proposal-crystal-language-system-wide/201104/2) * Owners: @renich **Owners, do not implement this work until the FESCo vote has explicitly ended.** When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the [FESCo ticket policy](https://docs.fedoraproject.org/en-US/fesco/#_ticket_policy) and the [Changes policy](https://docs.fedoraproject.org/en-US/program_management/changes_policy/) for more information. If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update. **REMINDER**: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the [Fedora Devel](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/) mailing list.
Author
Owner

cc @renich

cc @renich
Member

+1

+1
Member

I expect shard sources as RPM packages to be as painful as it is/was for Rust/Go.

But I will not block this from happening if folks want to maintain it that way so:

+1

I expect shard sources as RPM packages to be as painful as it is/was for Rust/Go. But I will not block this from happening if folks want to maintain it that way so: +1
Member

+1

In practice it's OK-ish for Rust, and we have an escape hatch for vendoring if that is impractical. in Golang it is harder...

So I'd rather try to package things Rust style first, and if it proves impractical then we can recommend bundling by default down the road.

+1 In practice it's OK-ish for Rust, and we have an escape hatch for vendoring if that is impractical. in Golang it is harder... So I'd rather try to package things Rust style first, and if it proves impractical then we can recommend bundling by default down the road.
Member

+1

+1
Owner

+1

+1

@salimma wrote in #3690 (comment):

+1

In practice it's OK-ish for Rust, and we have an escape hatch for vendoring if that is impractical. in Golang it is harder...

So I'd rather try to package things Rust style first, and if it proves impractical then we can recommend bundling by default down the road.

We have both pathways covered. I, for one, would prefer it if vendoring was allowed. It's far more practical when it comes to air-gaped development.

I dunno if I am allowed to comment here. Let me know if I shouldn't.

@salimma wrote in https://forge.fedoraproject.org/fesco/tickets/issues/3690#issuecomment-1365869: > +1 > > In practice it's OK-ish for Rust, and we have an escape hatch for vendoring if that is impractical. in Golang it is harder... > > So I'd rather try to package things Rust style first, and if it proves impractical then we can recommend bundling by default down the road. We have both pathways covered. I, for one, would prefer it if vendoring was allowed. It's far more practical when it comes to air-gaped development. I dunno if I am allowed to comment here. Let me know if I shouldn't.
Member

APPROVED (+5, 0, -0)

APPROVED (+5, 0, -0)
Member
Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GFHSSFIROA734OAGCFUR6GYAEQFQPWQO/
salimma 2026-10-20 11:16:08 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
7 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fesco/tickets#3690
No description provided.