LINTIAN::PROCESSABLE::SOURCE::COMPONENTS(3)

πŸ’– Lintian::Processable::Source::Components πŸ’–

okay bestie, so this is a page from the Lintian manual β€” section 3, the Debian Package Checker corner of the world β€” and the module in question is Lintian::Processable::Source::Components. say it with me now: interface to orig tar components ✨


🌈 NAME 🌈

Lintian::Processable::Source::Components β€” literally just the interface to orig tar components. that's the whole vibe.


πŸŽ€ SYNOPSIS πŸŽ€

like, here's how you'd actually pull it into your code, no cap:

use Moo;

with 'Lintian::Processable::Source::Components';

πŸ¦‹ DESCRIPTION πŸ¦‹

so Lintian::Processable::Source::Components hands you an interface to all the data about upstream source components. it's giving "backstage pass to the tarball situation."

and here's the tea: most sources only use one tarball. one. singular. that's it. so if you were expecting a whole ensemble cast of tarballs, bestie, usually it's a solo act. πŸ’…


πŸ‘‘ INSTANCE METHODS πŸ‘‘

components

returns a reference to a hash containing information about source components listed in the .dsc file.

  • the key is the filename πŸ“
  • the value is the name of the component ✨

that's it, that's the method. keys and values, filename to component name, iconic behaviour honestly.


πŸ’œ AUTHOR πŸ’œ

originally written by Adam D. Barratt <adsb@debian.org> for Lintian. thank you king 🫢


🌸 SEE ALSO 🌸


okay so that's the whole page! go forth and inspect those source components, you absolute main character πŸ’–

this lil beauty was served up by Lintian v2.139.0ubuntu2, dated 2026-10-08 β€” and yes, it lives under Lintian::Pr...:Components(3) in the manual, iykyk πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from