16:00:28 #startmeeting fpc 16:00:28 Meeting started Thu Oct 19 16:00:28 2023 UTC. 16:00:28 This meeting is logged and archived in a public location. 16:00:28 The chair is geppetto. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:28 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:28 The meeting name has been set to 'fpc' 16:00:28 #meetingname fpc 16:00:28 The meeting name has been set to 'fpc' 16:00:28 #topic Roll Call 16:00:42 Hey. 16:00:53 Hey 16:00:55 #chair tibbs 16:00:55 Current chairs: geppetto tibbs 16:01:25 .hi 16:01:26 decathorpe: Something blew up, please try again 16:01:29 hello o/ 16:01:30 decathorpe: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:01:47 🥲️ 16:02:22 #chair decathorpe 16:02:22 Current chairs: decathorpe geppetto tibbs 16:02:32 decathorpe: always breaking things 16:03:30 despite my best efforts :) 16:08:58 #topic Open Floor 16:09:04 Anybody have anything this week? 16:09:21 I would appreciate feedback on the Rust Packaging Guidelines refresh, but other than that, no 16:10:17 https://pagure.io/packaging-committee/pull-request/1310 16:11:29 👀 … that's big 16:11:57 I don't suppose you have a tl;dr for parts of it? 16:12:02 Yeah, it's huge. 16:12:04 yeah :( Rust is being used in more and more use cases, and they aren't covered by the current guidelines at all 16:12:53 TL;DR would probably be ... use rust2rpm to generate your spec files, it's designed to produce packages that comply with packaging guidelines 16:13:12 +1 then :) 16:16:59 Had a quick look through and it seems +1 … was a little confused by: 16:17:05 https://hackmd.io/@decathorpe/FedoraRustPackagingGuidelines#Subpackages-for-crate-features 16:17:50 Do you have an example of what that is? 16:18:50 for example, some crates are used internally to the Rust standard library, and have "feature flags" for this use case. these flags are useless (and broken) when building them outside this context, so they should not be exposed 16:19:26 👀 rust-zip* … So this is for libraries only? 16:20:02 please elaborate? 16:21:00 These create feature subpackages will always end in -devel? 16:21:06 yes 16:21:18 they are rust-$crate+$feature-devel 16:21:24 * geppetto nods 16:21:36 I'm pretty much +1 then 16:23:30 fwiw, almost everything from the current guidelines is also in the new ones, just structured differently. I tried to not introduce any new rules (or drop existing ones) 16:23:38 * geppetto nods 16:24:19 Really the only way to make it easy to review was to reorganize without changes and then build changes on top of that. Which is quite a pain. 16:24:45 Are the examples just gone completely? 16:24:50 Or add the new stuff and then reorganize … which is even more painful. 16:25:07 yeah. the examples are gone. nobody remembered to update them 16:25:28 As is often the fate of examples. 16:26:00 in this case, they are also not really worth much. they're almost verbatim what you get when you run "rust2rpm" for these projects 16:26:19 (or at least, they *were*, for an ancient version of rust2rpm) 16:34:13 Can rust2rpm take a url? 16:34:58 Maybe worth having a "for an example run: rust2rpm url-known-good-crate"? 16:35:25 Either way, unless anyone has anything else I'll end it for this week 16:36:50 Did we have anything else to say about the Go naming issue? 16:37:19 I had nothing to add to the comments, or what we said last week 16:37:30 Yeah, and I don't think there was any update. 16:38:06 #endmeeting