Bug 1900398 - Review Request: rust-libc-print - Println! and eprintln! macros on libc without stdlib
Summary: Review Request: rust-libc-print - Println! and eprintln! macros on libc witho...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1900400
TreeView+ depends on / blocked
 
Reported: 2020-11-22 18:08 UTC by Olivier Lemasle
Modified: 2021-01-11 21:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-11 21:45:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Olivier Lemasle 2020-11-22 18:08:37 UTC
Spec URL: https://olem.fedorapeople.org/reviews/rust-libc-print.spec
SRPM URL: https://olem.fedorapeople.org/reviews/rust-libc-print-0.1.14-1.fc33.src.rpm

Description:
Println! and eprintln! macros on libc without stdlib.

Fedora Account System Username: olem

Comment 1 Olivier Lemasle 2020-11-22 18:08:40 UTC
This package built on koji:  https://koji.fedoraproject.org/koji/taskinfo?taskID=56074742

Comment 2 Fabio Valentini 2020-12-18 11:33:24 UTC
I'm working on packaging an overlapping set of Rust crates (and submitted some of them as tickets already, d'oh!, I will close them as DUPLICATE and review your packages instead, if you want), but I found that libc-print is actually not required for ctor. It's only used in one of the examples, but not in the actual library code. You can safely remove that example file and the libc-print dependency, see: https://bugzilla.redhat.com/show_bug.cgi?id=1907081

Comment 3 Olivier Lemasle 2021-01-11 21:45:53 UTC
Thank you Fabio, you're right, that package was not necessary for packaging ctor.
And thank you for having closed my duplicated tickets; you were quicker to be reviewed!


Note You need to log in before you can comment on or make changes to this bug.