I've been looking through the ExtUtils::Manifest package and it does not appear that you can.
Line 189 (in the maniread sub) splits a MANIFEST line with this code:
my($file, $comment) = /^(\S+)\s*(.*)/;
It looks like anything after the first set of spaces is considered a comment.

Update:
After further investigation it looks like the open statement in the cp_if_diff sub might be the problem. The open statement is:
open(F,"< $from\0") or die "Can't read $from: $!\n";
If there was some way to represent a file with spaces using escape sequences (eg \x20, \040 ...) that would make this command open a file then it should work.

In reply to Re: MANIFEST with spaces in filenames? by mifflin
in thread MANIFEST with spaces in filenames? by coppit

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.