use Regexp::Assemble;
my $patterns = "/path/to/file.txt";
my $list_regex = Regexp::Assemble->new(file => $patterns);
$list_regex->track( 1 );

open( FILE, "<", "$arg1") or die "$arg1: $!\n";
while (<FILE>) {
    if (/$list_regex/) {print "\n$arg1\n$list_regex->matched\n";}
    }
close(FILE);
}
[download]

my $patterns = "/path/to/file.txt";
my $arg1 = shift;

open( PATTERNS, "<", $patterns ) or die "$patterns: $!\n";
my @list_patterns = <PATTERNS>;
close PATTERNS;
chomp @list_patterns;

my $regexStr = "(" . join("|", @list_patterns) . ")";
    my $list_regex = qr{$regexStr}i;
    
    open( FILE, "<", "$arg1") or die "$arg1: $!\n";
    while (<FILE>) {
        if (/$list_regex/) {print "\n$arg1\n$1\n";}
        }
    close(FILE);
[download]

part1.*part2
[download]

fggffgfg
part1
hghggh
ghhggh
hggh


part2
ytyty
[download]

You say that you "need /s so . to match newlines as well", and I assume this means that if your pattern list includes something like foo.*?bar, you would want that to match either of the following examples (where I'll put parens around the intended match):

example 1: blah (foobar) blah

example 2: blah (foo
all sorts of content on
lots of lines
of data 
bar) blah
[download]

In that case, you need to read the data file in slurp mode:

my $regex_string = join '|', @list_patterns;

open( FILE, "<", $arg1 ) or die "$arg1: $!";
$_ = do { local $/; <FILE> };  # temporarily set $/ = undef to slurp f
+ile
close FILE;

if ( /($regex_string)/is ) {
    # got a match...
}
[download]

Regarding the placement of parens and regex qualifiers, you could do that in other ways, like:

my $list_regex = qr/($regex_string)/is;
...
if ( /$list_regex/ ) {
...
[download]

No difference, really, but when there's a choice, I like having the parens visible in the code near the place where I use $1, $2, etc.