I'll explain in english what I need.

That can be useful but it's fuzzy. Far better to write tests which may or may not work. See How to ask better questions using Test::More and sample data

If you can negate the logic then (from your fuzzy description) I think it should be quite simple:

use strict;
use warnings;

use Test::More;

my @good = qw/PKG_CONFIG_PATH  XDG_DATA_DIRS/;
my @bad = qw/XDG_SEAT_PATH XDG_SESSION_PATH/;

plan tests => @good + @bad;

my $re = qr/^XDG.*PATH$/;

for my $str (@good) {
    unlike $str, $re, "good $str does not match";
}

for my $str (@bad) {
    like $str, $re, "bad $str matches";
}

[download]

🦛

In reply to Re: Driving the Engine right off the road by hippo
in thread Driving the Engine right off the road by Intrepid

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.