Test::Lintian::Templates(3)

💖 Test::Lintian::Templates(3) 💖

okay bestie so this one is from the Debian Package Checker manual, section 3, and it's literally the little helper module that handles templates 💅 like the glue that goes brrr between a .in file and the file it's supposed to become. no cap.

---

✨ NAME ✨

Test::Lintian::Templates — helper routines dealing with templates 🌸

---

🦋 SYNOPSIS 🦋

use Test::Lintian::Templates qw(fill_template);

my $data = { 'placeholder' => 'value' }; my $file =
'/path/to/generated/file';

fill_template("$file.in", $file, $data);

so you import fill_template, you make yourself a $data hashref with the placeholder values, you point $file at where the generated file should live, and then you just… call it. that's the whole vibe ✨

---

🌈 DESCRIPTION 🌈

Routines for dealing with templates in Lintian test specifications. it's giving infrastructure, it's giving plumbing, and honestly? we're obsessed 🫶

---

👑 FUNCTIONS 👑

💜 copy_skeleton_template_sets(INSTRUCTIONS, RUN_PATH, SUITE, TEST_SET)

Copies template sets belonging to SUITE into the test working directory RUN_PATH according to INSTRUCTIONS.

and what are those instructions, you ask? the target directory relative to RUN_PATH, followed by the name of the template set in parentheses. and if you want multiple of them? separate them with commas, periodt. 🔥

---

💜 remove_surplus_templates(SRC_DIR, TARGET_DIR)

Removes from TARGET_DIR any templates that have corresponding originals in SRC_DIR. spring cleaning but make it automated 🧹 ✨

---

💜 fill_skeleton_templates(INSTRUCTIONS, HASH, EPOCH, RUN_PATH, TEST_SET)

Fills the templates specified in INSTRUCTIONS using the data in HASH. 🍓

but here's the catch — it only fills templates when the generated files are not present or are older than either the file modification time of the template or the age of the data as evidenced by EPOCH. no wasted work, we love an efficient queen 💅

the INSTRUCTIONS are the target directory relative to RUN_PATH followed by the name of the whitelist in parentheses, and multiple instructions must be separated by commas.

---

💜 fill_whitelisted_templates(DIR, WHITE_LIST, HASH, HASH_EPOCH)

Generates all files in array WHITE_LIST relative to DIR from their templates — which are assumed to have the same file name but with extension .in — using data provided in HASH. 🌸

and the optional argument HASH_EPOCH? you can use it to preserve files when no generation is necessary. lowkey genius. 😌

---

💜 fill_all_templates(HASH, DIR)

Fills all templates in DIR with data from HASH. all of them. every single one. go big or go home 🔥

---

💜 fill_template(TEMPLATE, GENERATED, HASH, HASH_EPOCH, DELIMITERS)

Fills template TEMPLATE with data from HASH and places the result in file GENERATED. ✨

when you give it HASH_EPOCH, it will evaluate beforehand whether a substitution is even necessary, based on file modification times. so it checks first, then acts — main character energy honestly 🎀

and the optional parameter DELIMITERS? that one lets you change the standard delimiters, iykyk 🌟

---

💖 reminder bestie: delimiters matter, epochs matter, and modification times are always watching. read the args, love the args, pass them in the right order. 🫶

---

and that's the whole page, fr fr 💜 brought to you by Lintian v2.139.0ubuntu2, dated 2026-10-08 — go forth and template responsibly, you absolute icon 👑🌈