Bug #116698 for Test-Smoke: Where should Test::Smoke be installed?

Wed Aug 03 14:43:01 2016 jkeenan [...] cpan.org - Ticket created

Subject:

Where should Test::Smoke be installed?

http://search.cpan.org/~abeltje/Test-Smoke-1.70/README states: "The Test::Smoke suite has been designed to be installed outside of the normal Perl library-tree." I suspect that is why, when I today tried to install Test::Smoke with 'cpanm Test::Smoke', 'cpanm' timed out. I examined the Makefile.PL and noticed that it explicitly prompts the user to determine where the distribution should be installed. But that begs the question: "Where *should* Test::Smoke be installed?" Where is the best place "outside of the normal Perl library-tree" to put it? The docs are silent on this and should be clarified. Here's my specific use case: I have installed FreeBSD 10.3 in a VirtualBox VM on a Linux x86-64 host. I have never previously sent smoke reports about Perl itself. (Linux is sufficiently well covered.) But now I am considering doing smoke-testing for Perl 5 blead (and perhaps for smoke-me branches) on this FreeBSD installation. I have not yet used something like 'perlbrew' or 'plenv' to re-set my "everyday perl, so my everyday perl is 5.20.3 found at /usr/local/bin/perl. I have a git checkout of perl underneath my home directory at ~/gitwork/perl/. Let's assume that at first I only want to send smoke reports episodically, i.e., kicked off manually rather than by a cron job set to a particular time of day or upon detection of a new commit to blead. How and where should I install Test::Smoke for that purpose? Thank you very much. Jim Keenan

Thu Aug 25 07:58:53 2016 abe.timmerman [...] xs4all.nl - Correspondence added

Subject:	Re: [rt.cpan.org #116698] Where should Test::Smoke be installed?
Date:	Thu, 25 Aug 2016 14:58:35 +0300
To:	bug-Test-Smoke [...] rt.cpan.org
From:	Abe Timmerman <abe.timmerman [...] xs4all.nl>

Subject:	Re: [rt.cpan.org #116698] Where should Test::Smoke be installed?
To:	bug-Test-Smoke [...] rt.cpan.org
From:	Abe Timmerman <abe.timmerman [...] xs4all.nl>

On 03-08-16 21:43, James E Keenan via RT wrote: Show quoted text

> Wed Aug 03 14:43:01 2016: Request 116698 was acted upon.

Hi Jim, Sorry it took me so long to answer your question. Show quoted text

> Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=116698 > > > > http://search.cpan.org/~abeltje/Test-Smoke-1.70/README states: > > "The Test::Smoke suite has been designed to be installed outside of the normal Perl library-tree." > > I suspect that is why, when I today tried to install Test::Smoke with 'cpanm Test::Smoke', 'cpanm' timed out. I examined the Makefile.PL and noticed that it explicitly prompts the user to determine where the distribution should be installed.

This can be prevented by setting the environment variables: PERL_MM_USE_DEFAULT=1 SMOKE_INSTDIR=<install-dir> Show quoted text

> But that begs the question: "Where *should* Test::Smoke be installed?" Where is the best place "outside of the normal Perl library-tree" to put it? The docs are silent on this and should be clarified.

This is a matter of personal taste/setup. I can tell you how I did set up my smokeboxes: ~/TestSmoke/bin This is my install-dir ~/TestSmoke/etc This is my configs and logs dir ~/TestSmoke/etc/logs logdir ~/TestSmoke/perl-git git main-clone ~/TestSmoke/perl-current git clone (from ../perl-git) to smoke After installing Test::Smoke I go to the ~/TestSmoke/etc directory and run: ../bin/configsmoke.pl -p blead Show quoted text

> Here's my specific use case: I have installed FreeBSD 10.3 in a VirtualBox VM on a Linux x86-64 host. I have never previously sent smoke reports about Perl itself. (Linux is sufficiently well covered.) But now I am considering doing smoke-testing for Perl 5 blead (and perhaps for smoke-me branches) on this FreeBSD installation. I have not yet used something like 'perlbrew' or 'plenv' to re-set my "everyday perl, so my everyday perl is 5.20.3 found at /usr/local/bin/perl. I have a git checkout of perl underneath my home directory at ~/gitwork/perl/.

All reports are welcome! Show quoted text

> Let's assume that at first I only want to send smoke reports episodically, i.e., kicked off manually rather than by a cron job set to a particular time of day or upon detection of a new commit to blead. How and where should I install Test::Smoke for that purpose?

Every run of the configsmoke.pl script (with different prefix) results in a shell script that can be started manually (eg: nohup ./blead.sh &) If you want your cron to be installed later, just rerun configsmoke with the same prefix argument, and answer all the questions up to the cron point with <enter> and have configsmoke set your cron... I hope this helps! Good luck, Abe. -- \|||/ | "Are you pondering what I'm pondering, Pinky?" (o o) | Sure, Brain, but how are we going to find chaps our +-ooO-( )-Ooo-+ size? (10 Nov 93 - Spell-Bound) |

Download signature.asc
application/pgp-signature 181b

Message body not shown because it is not plain text.

Thu Aug 25 07:58:53 2016 The RT System itself - Status changed from 'new' to 'open'

Fri Apr 21 12:07:28 2017 abeltje [...] cpan.org - Correspondence added

Not really a bugreport.

Fri Apr 21 12:07:34 2017 abeltje [...] cpan.org - Status changed from 'open' to 'resolved'