Packaging Guidelines #5

Open
opened 2017-02-26 21:08:20 +00:00 by ignatenkobrain · 1 comment
Contributor

So, we need to have packaging guidelines. At this point I found things to note:

  • Template should be same as generated by rust2rpm
  • Do not package crates which will not be used
    • Non-linux
    • Nightly
  • Patch metadata to not have "target(windows)" and such
  • Try to update dependencies to latest versions first
  • If you do patches, send upstream (this is obvious)
  • Follow all other Packaging Guidelines (this is obvious as well)

Something else in mind?

So, we need to have packaging guidelines. At this point I found things to note: - Template should be same as generated by rust2rpm - Do not package crates which will not be used - Non-linux - Nightly - Patch metadata to not have "target(windows)" and such - Try to update dependencies to latest versions first - If you do patches, send upstream (this is obvious) - Follow all other Packaging Guidelines (this is obvious as well) Something else in mind?
Owner

I'd like for us to use the SPDX identifiers right from the get-go. I've requested an exception from Fedora Legal, but I've not gotten any responses yet.

I'd like for us to use the SPDX identifiers right from the get-go. [I've requested an exception from Fedora Legal](https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org/thread/IF3ZSIUBFXN24XOJTL7CLQVB66ATRTYY/), but I've not gotten any responses yet.
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
2 participants
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
rust/sig-archive#5
No description provided.