Change: Crystal Language #3690
Labels
No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
7 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fesco/tickets#3690
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
cc @renich
+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
+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
+1
@salimma wrote in #3690 (comment):
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.
APPROVED (+5, 0, -0)
Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GFHSSFIROA734OAGCFUR6GYAEQFQPWQO/