Sponsored Content
Full Discussion: Doom777
Contact Us Post Here to Contact Site Administrators and Moderators Doom777 Post 303031231 by DOOM777 on Sunday 24th of February 2019 06:38:04 PM
Old 02-24-2019
Doom777

Originally Posted by Naky
... (I can't put the name of the professor because is against the school rules to share private details of person related to the school, which includes the name)

I
 
Module::Install::ManifestSkip(3pm)			User Contributed Perl Documentation			Module::Install::ManifestSkip(3pm)

SYNOPSIS
use inc::Module::Install; all_from 'lib/Foo.pm'; manifest_skip; WriteAll; DESCRIPTION
This module generates a "MANIFEST.SKIP" file for you (using Module::Manifest::Skip) that contains the common files that people do not want in their "MANIFEST" files. The SKIP file is generated each time that you (the module author) run "Makefile.PL". You can add your own custom entries at the top of the "MANIFEST" file. Just put a blank line after your entries, and they will be left alone. This module also adds 'MANIFEST' to the "clean_files()" list so that "make clean" will remove your "MANIFEST". OPTIONS
If you don't plan on adding anything to the stock MANIFEST.SKIP and just want "make clean" to delete it, say this: manifest_skip 'clean'; THEORY
One school of thought for release management is that you never commit your "MANIFEST" file. You just generate it using "make manifest", right before releasing a module, and then delete it afterwards. This is good because you never forget to add new files to your "MANIFEST". The only problems are that you always need to generate a "MANIFEST.SKIP" file, and you need to add "MANIFEST" to your clean_files, or delete it by hand. This module does these things for you. perl v5.14.2 2011-09-25 Module::Install::ManifestSkip(3pm)
All times are GMT -4. The time now is 04:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy