CONFIGSMOKE(1)
π CONFIGSMOKE π
okay so, bestie, welcome to configsmoke β straight outta User Contributed Perl Documentation, manual section 1. She's here to explain all the options while you're doing your configuration, and she's very thorough. π«Ά
πΈ NAME πΈ
configsmoke β Explain the options during configuration. That's it, that's the whole vibe. π
π VERSION π
This is version: 0.094
β¨ SYNOPSIS β¨
Software installed in ~/perl5coresmoke/smoke:
$ cd ~/perl5coresmoke
$ mkdir etc
$ cd etc
$ ../smoke/tsconfigsmoke.pl -c <prefix>
or on MSWin32 (installed in %HOMEDRIVE%%HOMEPATH%\perl5coresmoke\smoke):
%HOMEDRIVE%
cd %HOMEPATH%\perl5coresmoke
md etc
cd etc
..\smoke\tsconfigsmoke.bat -c <prefix>
π OPTIONS π
--config|-c <prefix>β set the prefix for all related files--desβ use all the default settings, no questions asked (she's not gonna bother you, she's just gonna do it)--help|-hβ the short help for options--show-configβ show the current values for these options
π DESCRIPTION π
Welcome to the Perl5 core smoke suite π
Test::Smoke is the symbolic name for a set of scripts and modules that try to run the perl core tests on as many configurations as possible and combine the results into an easy to read report. iconic behavior, honestly.
The main script is tssmokeperl.pl, and this uses a configuration file that is created by this program (tsconfigsmoke.pl). There is no default configuration as some actions can be rather destructive π so you will need to create your own configuration by running this program!
By default the configuration file created is called smokecurrent_config, this can be changed by specifying the -c <prefix> switch at the command line.
$ perl ../smoke/configsmoke.pl -c mysmoke
will create mysmoke_config (in the current directory) as the configuration file and use mysmoke as prefix for related files.
The configfile is written with Data::Dumper, so it is a bit of Perl that will be put through eval() when read back for use. no cap.
After you are done configuring, a job command list (JCL) is written. For MSWin32 this is called <prefix>.cmd, for VMS this is called <prefix>.COM, otherwise this is called <prefix>.sh.
All output (stdout, stderr) from tssmokeperl.pl and its sub-processes is redirected to a logfile called <prefix>.log by the JCL.
This is a new version of the configure script, SOME THINGS ARE DIFFERENT! π
You will be asked some questions in order to configure this smoke suite. Please make sure to read the documentation perldoc configsmoke in case you do not understand a question.
- Values in angled-brackets (
<>) are alternatives (none other allowed) - Values in square-brackets (
[]) are default values (<Enter>confirms) - Use single space to clear a value
- Answer
'&-d'to continue with all default answers
π¦ ddir
ddir is the destination directory. This is used to put the source-tree in and build perl. If a source-tree appears to be there you will need to confirm your choice. (she's checking up on you, respectfully.)
π¦ w32args
For MSWin32 we need some extra information that is passed to Test::Smoke::Smoker in order to compensate for the lack of Configure.
Items involved:
w32cc: This is theCCTYPE(GCC|MSVC|BORLAND)w32make: This is themakeprogram (gmake|nmake)w32args: Arrayref with:--win32-cctype,w32cc--win32-maker,w32makeosvers=$osversccversarg
See also Configure_win32( ) in Test::Smoke::Util and tsw32configure.pl
π¦ sync_type
We have dropped support for the sync_types: snapshot and hardlink. gone, deceased, not coming back π«Ά
sync_type can be one of three:
git (preferred)
This will use the git program to clone the master perl-source from GitHub into gitdir (the master can be changed gitorigin). For the actual smoking, yet another clone into ddir is used.
Items involved:
gitbin: Absolute location of thegitprogram.gitorigin: The origin of the Perl5 source tree (https://github.com/Perl/perl5.git).gitdir: Absolute location for the main clone of gitorigin (perl-from-git).gitdfbranch: The branch in the repository to smoke (blead).gitbranchfile: Absolute location of the file that can hold the name of the branch to actually smoke (<prefix>.gitbranch).
rsync
This will use the rsync program to sync up with the repository. tsconfigsmoke.pl checks to see if it can find rsync in your path.
The default switches (opts) passed to rsync are: -az --delete
Items involved:
rsync: Absolute location of thersyncprogram.opts: Options to pass to rsync (-az --delete).source: Hostname:port/directory of the source (rsync://dromedary.p5h.org:5872/perl-current/)
copy
This will use File::Copy and File::Find to just copy from a local source directory (cdir).
Items involved:
cdir: Absolute location of the source tree on the local system.
See also Test::Smoke::Syncer
π¦ make finetuning
Two different config options to accomodate the same thing: parallel build and serial testing
makeopt: used byTest::Smoke::Smoker::_make()testmake: Use a different binary formake _test
π¦ harnessonly
harnessonly indicates that make test is replaced by make test_harness.
π¦ harness3opts
harness3opts are passed to HARNESS_OPTIONS for the make test_harness step.
π¦ force_c_locale
force_c_locale is passed as a switch to tsrunsmoke.pl to indicate that $ENV{LC_ALL} should be forced to C during make test.
π¦ defaultenv
defaultenv, when set will make tsrunsmoke.pl remove $ENV{PERLIO} and only do a single pass make test.
π¦ perlio_only
perlio_only, when set wil not run the tests with $ENV{PERLIO}=stdio and only with $ENV{PERLIO}=perlio (and with locale-setting if set).
π¦ locale
locale and its value are passed to tsrunsmoke.pl and its value is passed to tsreporter.pl. tsrunsmoke.pl will do an extra pass of make test with $ENV{LC_ALL} set to that locale (and $ENV{PERL_UNICODE}="", $ENV{PERLIO}=perlio). This feature should only be used with UTF8 locales, that is why this is checked (by regex only).
If you know of a way to get the utf8 locales on your system, which is not covered here, please let me know! π
π¦ skip_tests
This is a MANIFEST-like file with the paths to tests that should be skipped for this smoke.
The process involves on the fly modification of MANIFEST for tests in lib/ and ext/ and renaming of core-tests in t/.
π¦ smokedb_url
Instead of flooding a mailing list, reposts should be sent to the Perl5CoreSmokeDB. The option to mail yourself a copy of the report still exists. The Perl5CoreSmokeDB however offers a central point of view to the smoke results.
Items involved:
smokedb_url: Where to post the report (https://perl5.test-smoke.org/report).send_log: Can be one of always|on_fail|never (on_fail).send_out: Can be one of always|on_fail|never (never).
π¦ mail
The (boolean) option mail is used to see if the report is send via mail.
Items involved:
mail_type: Can be one of: sendmail|mail|mailx|sendemail|Mail::Sendmail|MIME::Lite depending on which of these is available.
See Test::Smoke::Mailer.
to: Email address to send the report to.cc: Email address to send a carbon copy of the report to.bcc: Email address to send a blind carbon copy of the report to.ccp5p_onfail: Boolean to indicate if this report should be send to the perl5porters mailing list, please don't do that (unless they ask for it). π«mailbin: Absolute location of themailprogram is set as mailt_ype.mailxbin: Absolute location of themailxprogram if set as mail_type.swcc:mailxcommand line switch for the CC email address (-c).swbcc:mailxcommand line switch for the BCC email address (-b).
sendemailbin: Absolute location of thesendemailprogram if set as mail_type.from: Email address to use in FROM.mserver: The hostname of the SMTP server to use (localhost).msport: The port on that host the SMTP servers uses (25).msuser: The username for authenticating with the SMTP server.mspass: The password for authenticating with the SMTP server.
sendmailbin: Absolute location of thesendmailprogram if set as mail_type.
Extra options: from
mail_type: Mail::Sendmail
Extra options: from|mserver|msport
mail_type: MIME::Lite
Extra options: from|mserver|msport|msuser|mspass
π¦ Various files/directories
This section only handles the adir option interactively, but more options are set.
adir: Absolute location to use as a base for the archive of reports and other files, leave empty for no archiving. We archive outfile, rptfile, jsnfile and logfile.outfile: The file that holds all information to create the report (mktest.out).rptfile: The report that is generated at the end of the run (mktest.rpt).jsnfile: The json that will be send to the Perl5CoreSmokeDB (mktest.jsn).lfile: Absolute location of the logfile (<prefix>.log).
π¦ hostname
By default we use the hostname reported by System::Info, but this can be changed here.
π¦ un_file
One can add a usernote to the report, this usernote is kept in a file (<prefix>.usernote).
If the file does not exist, it will be created.
π¦ un_position
This is the position (top|bottom) where the usernote is inserted into the report (bottom).
π¦ cronbin
On unix-like systems we will check for the crontab program, on MSWin32 we will check for either the schtasks.exe or at.exe program.
crontab
For crontab we read the current entries and if we find ourselfs (the JCL) we will comment that line out and add a new line.
schtasks.exe
For schtasks we query the scheduler to see if our TaskName is already in the schedule and if so we will add the /F command line switch to override the current entry.
One can find the scheduled task by name: P5Smoke-<prefix> or a general schtasks /query | find "P5Smoke-"
at.exe
Microsoft has removed at.exe from Windows 10+ so we can no longer really maintain this feature and schtasks.exe is preferred. π rip.
π¦ crontime
This is a HH::MM formated time.
π¦ v
This option indicates the verbosity towards the logfile (lfile) and can be set to: 0|1|2, the default is 1.
smartsmokeβ bestie, this one is the vibe check β¨ it means the smoke doesn't even need to run if the patchlevel (aka the git commit sha) is still the same after syncing the source-tree. Like, no changes? No smoke. Iconic.killtimeβ when$Config{d_alarm}is found, we can usealarm()to abort long-running smokes π leave this value empty to keep the old behaviour, fr fr.
07:30 => tssmokeperl.pl is aborted at 7:30 localtime
+23:45 => tssmokeperl.pl is aborted after 23 hours and 45 minutes
Thank you Jarkko for donating this suggestion π«Ά we love a generous king.
umaskβ whatever you put here gets set in the shell-script that starts the smoke πreniceβ this one adds a line in the shell-script that starts the smoke πΈPERL5LIBβ if you've got a value forPERL5LIBset in the config environment, you could have it transferred to the JCL π do not bother asking if it is not there β if it's not there, it's not there, periodt.PERL5OPTβ same energy: if you have a value forPERL5OPTset in the config environment, you could have it transferred tho the JCL π and again, do not bother asking if it is not there.cfgβ"cfg"is the path to the file that holds the build-configurations π there are several build-cfg files provided with the distribution:perlcurrent.cfg: for the blead-branch on unixy systems π§w32current.cfg: for the blead-branch on MSWin32 πͺvmsperl.cfg: for the blead-branch on OpenVMS π
One of these files is used as the default build configurations file, depending on the OS one is on π
β¨ COMMAND LINE OPTIONS Makefile.PL β¨
--site-libβ this will leave the"PREFIX"and"INSTALLSITESCRIPT"as-is and install as a regular Perl module π no cap.
π¦ ENVIRONMENT VARIABLES π¦
These change the behaviour of Makefile.PL, bestie:
SMOKE_INST_DIRβ sets"PREFIX"and"INSTALLSITESCRIPT"to this directory πSMOKE_INST_SITE_LIBβ when true, will leave"PREFIX"and"INSTALLSITESCRIPT"as is, and install as a regular Perl module. No questions asked π β¨PERL_MM_OPTβ this may contain"INSTALL_BASE="that needs to be honoured πAUTOMATED_TESTINGβ when true, will not ask for the installation dir and use whatever default is in place π€ very main character of it.
π COPYRIGHT π
Β© MMII - MMXXIII Abe Timmerman <abeltje@cpan.org> π«Ά
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself πΈ
See:
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY π without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. So likeβ¦ use it, love it, but don't come for the author if it misbehaves, bestie π
That's the whole page, babes β written against perl v5.42.0, dated 2025-07-25, and it lives in section CONFIGSMOKE(1) π
β¨ go forth and smoke responsibly ππ¦
π¦ where this page comes from
- fedora 43: perl-Test-Smoke 1.84-2.fc43 Β· GPL-1.0-or-later OR Artistic-1.0-Perl
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms