RPM::G...Patches(3pm)

🌸 NAME 🌸

okay so, bestie, welcome to RPM::G...Patches — that's the 3pm one, the Perl module manpage in the User Contributed Perl Documentation set. 💖

and the name line? it's literally FIXME - FIXME. that's it. that's the whole thing. somebody was ✨gonna✨ write it and then... did not. 💀

---

✨ SYNOPSIS ✨

here's the whole vibe they left us:

use Fixme::FIXME;

....

yeah. use Fixme::FIXME; and then a .... because the author was like "you get it". 🙈 that is the entire synopsis, no cap.

---

💖 DESCRIPTION 💖

FIXME fixme fixme fixme

four words. that's the description. the whole description. i'm not even kidding. 😭

---

🎀 CONSTRUCTOR 🎀

the page says FIXME-only if OO right here — which is doing two jobs at once: it's a FIXME, and it's flagging that this whole section is only relevant if you're doing OO. so, OO corner of the page, bestie. 🫶

🧚 new( FIXME-args )

FIXME FIXME describe constructor — yes, the thing that's supposed to describe the constructor is itself a description placeholder. somebody please come finish this. 🙏

---

🔥 METHODS 🔥

the page's own note to itself: FIXME document methods. iconic honestly.

method1

...

method2

...

---

⭐ EXPORTED FUNCTIONS ⭐

heading is here. body is empty. ghost town. 👻 nothing written down.

---

🎀 EXPORTED CONSTANTS 🎀

same situation — heading present, content not. 🫶

---

🌈 EXPORTABLE FUNCTIONS 🌈

just a heading sitting there by itself, no content. 💅

---

🦋 FILES 🦋

heading only. no files listed. nothing. 🍓

---

💅 DIAGNOSTICS 💅

okay THESE are real and they're actually useful, so pay attention bestie:

• DuplicatePatch — you've got multiple definitions seen for "PatchNN". This is often caused by a %if in the specfile, but it could also be an unintentional duplication. so: either the specfile logic is doing it to you, or it's just an accident. either way, there are multiple definitions and that's the situation. 🔍
• BadPatchFuzz — overriding a patch's fuzz factor is a bad idea. for real. here's what it actually means: "those three lines of context that diff provides? Toss some of those away, and try again". and the consequence is you can end up with code that compiles but is silently corrupt 😭 — like it looks fine and it is NOT fine. There really is no reason for this. Why not take the time to regenerate your patches? genuinely, why not just regenerate them. 👑

---

💜 AUTHOR 💜

Ed Santiago <santiago@redhat.com> — that's the human. 🫶

---

and that's the page!! this one came to you from the User Contributed Perl Documentation, perl v5.42.0, dated 2025-07-25. stay slay, regenerate your patches, bye bestie 🎀✨