FWIW, it's a poorly crafted regex. It will make false matches; e.g.–

moo@cow>perl -le 'print "MATCH" if +shift =~ /.*\/(.*).lib/' ' /ohai/l
+ib/bingo'
MATCH
moo@cow>perl -le 'print "MATCH" if +shift =~ /.*\/(.*).lib/' 't a c o/
+alibrary.mp4'
MATCH

[download]

I presume it is meant to match and retain the plain lib name. This is saner but maybe not as good as it gets–

$lib_name =~ s{\A.+/([^/]+)\.lib\z}{$1};

I left out dot-star because you should if you can and if we know there will always be a slash before the lib (/lib) then we can assume there will always be *some* content before the slash (c.f., there is never going to be a volume:/lib dir). Lots more info: perlre.

In reply to Re: Regex explanation by Your Mother
in thread Regex explanation by ElectroRed

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.