> > > If I just use Win32::Process, then this would be a dependency also on Linux, which is unwanted

> And indeed, Proc::Background is pretty much exactly what I was hoping for. Thanks a lot!

Well ... Proc::Background relies on Win32::Process

package Proc::Background::Win32;
$Proc::Background::Win32::VERSION = '1.30';
# ABSTRACT: Windows-specific implementation of process create/wait/kil
+l

...

use Win32::Process qw( NORMAL_PRIORITY_CLASS INFINITE );   # <---

...

[download]

update

and that's how it's avoided as dependency on Linux

https://metacpan.org/release/NERDVANA/Proc-Background-1.30/source/dist.ini 

[OSPrereqs / MSWin32]
Win32::Process = 0.04
Win32::ShellQuote = 0.003001

[download]

Cheers Rolf
(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
Wikisyntax for the Monastery

In reply to Re^3: How to portably stop processes? (OSPrereqs) by LanX
in thread How to portably stop processes? by haj

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.