Config...License(3pm)

✨ Config...License β€” the manual page, but make it cute ✨

okay bestie, gather round, because this is Config::Model::models::Dpkg::Copyright::GlobalLicense and it's literally a Perl manual page from the Config::Model universe, section 3pm (that's the "perl module docs" section, iykyk). It lives in the User Contributed Perl Documentation corner of the man page world πŸ’…


πŸ’– NAME πŸ’–

Config::Model::models::Dpkg::Copyright::GlobalLicense β€” a Configuration class, like, the <rainbow>Dpkg::Copyright::GlobalLicense</rainbow> one specifically πŸŽ€


🌸 DESCRIPTION 🌸

These are configuration classes used by Config::Model. That's the whole vibe.

This particular one represents a license that can be applied to the whole package. And plot twist: this element can be omitted. It's optional, bestie, it's giving "no pressure" energy πŸ¦‹

🧚 Elements 🧚

⭐ short_name ⭐

So the Copyright and License fields in the header paragraph? They may complement but they do not replace the files paragraphs. Say it with me: complement, not replace πŸ™ˆ

What they're for: summarising the contributions and redistribution terms for the whole package. Classic use case is when a work combines a permissive license and a copyleft license (chaotic, iconic), or when you wanna document a compilation copyright and license.

Also, you can use only License in the header paragraph β€” but Copyright alone makes no sense. Zero sense. None. It's giving incomplete thoughts πŸ’€

Optional. Type: uniline.

Now here's the tea on the possible values β€” here are some explanations for you:

  • 'Apache' β€” Apache license. For versions, consult the Apache_Software_Foundation.
  • 'Artistic' β€” Artistic license. For versions, consult the Perl_Foundation.
  • 'BSD-2-clause' β€” Berkeley software distribution license, 2-clause version.
  • 'BSD-3-clause' β€” Berkeley software distribution license, 3-clause version.
  • 'BSD-4-clause' β€” Berkeley software distribution license, 4-clause version.
  • 'CC-BY' β€” Creative Commons Attribution license.
  • 'CC-BY-NC' β€” Creative Commons Attribution Non-Commercial.
  • 'CC-BY-NC-ND' β€” Creative Commons Attribution Non-Commercial No Derivatives.
  • 'CC-BY-NC-SA' β€” Creative Commons Attribution Non-Commercial Share Alike.
  • 'CC-BY-ND' β€” Creative Commons Attribution No Derivatives.
  • 'CC-BY-SA' β€” Creative Commons Attribution Share Alike license.
  • 'CC0' β€” Creative Commons Universal waiver.
  • 'CDDL' β€” Common Development and Distribution License. For versions, consult Sun Microsystems.
  • 'CPL' β€” IBM Common Public License. For versions, consult the IBM_Common_Public License_(CPL)_Frequently_asked_questions.
  • 'EFL' β€” The Eiffel Forum License. For versions, consult the Open_Source_Initiative.
  • 'Expat' β€” The Expat license.
  • 'FreeBSD' β€” FreeBSD Project license.
  • 'GFDL' β€” GNU Free Documentation License.
  • 'GFDL-NIV' β€” GNU Free Documentation License, with no invariant sections.
  • 'GPL' β€” GNU General Public License.
  • 'ISC' β€” Internet_Software_Consortium's license, sometimes also known as the OpenBSD License.
  • 'LGPL' β€” GNU Lesser General Public License, (GNU Library General Public License for versions lower than 2.1).
  • 'LPPL' β€” LaTeX Project Public License.
  • 'MPL' β€” Mozilla Public License. For versions, consult Mozilla.org.
  • 'Perl' β€” Perl license (equates to "GPL-1+ or Artistic-1").
  • 'Python-CNRI' β€” Python Software Foundation license. For versions, consult the Python_Software Foundation.
  • 'QPL' β€” Q Public License.
  • 'W3C' β€” W3C Software License. For more information, consult the W3C IntellectualRights FAQ and the 20021231 W3C_Software_notice_and_license.
  • 'ZLIB' β€” zlib/libpng_license.
  • 'Zope' β€” Zope Public License. For versions, consult Zope.org.

πŸ’œ full_license πŸ’œ

okay this one matters, listen up:

If you leave this blank here, then the file must include a stand-alone License section matching each license short name listed on the first line β€” see the Standalone License Section section. No skipping, no shortcuts 🫢

Otherwise, this field should either:

  • include the full text of the license(s), or
  • include a pointer to the license file under /usr/share/common-licenses.

And this field should include all text needed in order to fulfill both the Debian Policy requirement for including a copy of the software distribution license, and any license requirements to include warranty disclaimers or other notices with the binary package.

Optional. Type: string.


πŸ”₯ SEE ALSO πŸ”₯

  • cme

πŸ‘‘ AUTHOR πŸ‘‘

Dominique Dumont


2010 2011 Dominique Dumont


🌈 LICENSE 🌈

LGPL2


and that's the whole page, bestie! no cap, you now know everything this man page knows πŸ’–

signing off with the receipts: this was built against perl v5.42.3, dated 2026-08-30, and the page itself is Config...License(3pm) from the User Contributed Perl Documentation. slay, go forth and license responsibly βœ¨πŸ¦‹πŸ’…

πŸ“¦ where this page comes from