.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. .ie n \{\ . ds C` "" . ds C' "" 'br\} .el\{\ . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "Software::License::Custom 3pm" .TH Software::License::Custom 3pm 2024-02-14 "perl v5.38.2" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH NAME Software::License::Custom \- custom license handler .SH VERSION .IX Header "VERSION" version 0.104006 .SH DESCRIPTION .IX Header "DESCRIPTION" This module extends Software::License to give the possibility of specifying all aspects related to a software license in a custom file. This allows for setting custom dates, notices, etc. while still preserving compatibility with all places where Software::License is used, e.g. Dist::Zilla. .PP In this way, you should be able to customise some aspects of the licensing messages that would otherwise be difficult to tinker, e.g. adding a note in the notice, setting multiple years for the copyright notice or set multiple authors and/or copyright holders. .PP The license details should be put inside a file that contains different sections. Each section has the following format: .IP "header line" 4 .IX Item "header line" This is a line that begins and ends with two underscores \f(CW\*(C`_\|_\*(C'\fR. The string between the begin and the end of the line is first depured of any non-word character, then used as the name of the section; .IP body 4 .IX Item "body" a Text::Template (possibly a plain text file) where items to be expanded are enclosed between double braces .PP Each section is terminated by the header of the following section or by the end of the file. Example: .PP .Vb 10 \& _\|_[ NAME ]_\|_ \& The Foo\-Bar License \& _\|_URL_\|_ \& http://www.example.com/foo\-bar.txt \& _\|_[ META_NAME ]_\|_ \& foo_bar_meta \& _\|_{ META2_NAME }_\|_ \& foo_bar_meta2 \& _\|_{ SPDX_EXPRESSION }_\|_ \& foo_bar_spdx_expression \& _\|_[ NOTICE ]_\|_ \& Copyright (C) 2000\-2002 by P.R. Evious \& Copyright (C) {{$self\->year}} by {{$self\->holder}}. \& \& This is free software, licensed under {{$self\->name}}. \& \& _\|_[ LICENSE ]_\|_ \& The Foo\-Bar License \& \& Well... this is only some sample text. Verily... only sample text!!! \& \& Yes, spanning more lines and more paragraphs. .Ve .PP The different formats for specifying the section name in the example above are only examples, you're invited to use a consistent approach. .SH "PERL VERSION" .IX Header "PERL VERSION" This module is part of CPAN toolchain, or is treated as such. As such, it follows the agreement of the Perl Toolchain Gang to require no newer version of perl than one released in the last ten years. This version may change by agreement of the Toolchain Gang, but for now is governed by the Lancaster Consensus of 2013 and the Lyon Amendment of 2023 (described at the linked-to document). .PP Although it may work on older versions of perl, no guarantee is made that the minimum required version will not be increased. The version may be increased for any reason, and there is no promise that patches will be accepted to lower the minimum required perl. .SH METHODS .IX Header "METHODS" .SS new .IX Subsection "new" .Vb 1 \& my $slc = Software::License::Custom\->new({filename => \*(AqLEGAL\*(Aq}); .Ve .PP Create a new object. Arguments are passed through an anonymous hash, the following keys are allowed: .PP .Vb 1 \& filename \- the file where the custom software license details are stored .Ve .SS load_sections_from .IX Subsection "load_sections_from" .Vb 1 \& $slc\->load_sections_from(\*(AqMY\-LEGAL\-ASPECTS\*(Aq); .Ve .PP Loads the different sections of the license from the provided filename. .PP Returns the input object. .SS section_data .IX Subsection "section_data" .Vb 1 \& my $notice_template_reference = $slc\->section_data(\*(AqNOTICE\*(Aq); .Ve .PP Returns a reference to a textual template that can be fed to Text::Template (it could be simple text), according to what is currently loaded in the object. .SH "MORE METHODS" .IX Header "MORE METHODS" The following methods, found in all software license classes, look up and render the template with the capitalized form of their name. In other words, the \f(CW\*(C`license\*(C'\fR method looks in the \f(CW\*(C`LICENSE\*(C'\fR template. .PP For now, the \f(CW\*(C`meta_name\*(C'\fR and \f(CW\*(C`meta2_name\*(C'\fR methods return \f(CW\*(C`custom\*(C'\fR if called on the class. This may become fatal in the future. .IP \(bu 4 name .IP \(bu 4 url .IP \(bu 4 meta_name .IP \(bu 4 meta2_name .IP \(bu 4 license .IP \(bu 4 notice .IP \(bu 4 fulltext .IP \(bu 4 version .SH AUTHOR .IX Header "AUTHOR" Ricardo Signes .SH "COPYRIGHT AND LICENSE" .IX Header "COPYRIGHT AND LICENSE" This software is copyright (c) 2024 by Ricardo Signes. .PP This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.