> "Barbie" == Barbie <[EMAIL PROTECTED]> writes:
Barbie> Another thing to bear in mind ... is this a Unix-like only
Barbie> module? If not, then symlinks will be a no go. Win32 doesn't
Barbie> support them, and I would imagine there are other OSs in the
Barbie> same position.
It's not my int
On 18 December 2003 21:44 Randal L. Schwartz wrote:
> I can add local symlinks
> and hardlinks. I'll compute ownership out-of-band and compare it
> to the test result though... I wouldn't want someone extracting
> this as joebloe to fail because the uid wasn't root. :)
Another thing to bear in m
Op een winterige herfstdag (Thursday 18 December 2003 22:44), schreef Randal
L. Schwartz:
> > "Michael" == Michael G Schwern <[EMAIL PROTECTED]> writes:
>
> Michael> If you're not planning on your tests modifying the test tree at
> all, Michael> you can probably just get away with having t/tr
> "Michael" == Michael G Schwern <[EMAIL PROTECTED]> writes:
Michael> If you're not planning on your tests modifying the test tree at all,
Michael> you can probably just get away with having t/tree/... as a bunch of
Michael> normal files and directorys in the tarball. Don't ship a seperate
Mi
On Thu, Dec 18, 2003 at 01:28:57PM -0800, Randal L. Schwartz wrote:
> In my recently released File::Finder module, I have the basic
> tests to ensure that the find options are grabbed correctly,
> and that the core and/or/not/parens logic is clean, along with
> the easy test to ensure that eval() w
In my recently released File::Finder module, I have the basic
tests to ensure that the find options are grabbed correctly,
and that the core and/or/not/parens logic is clean, along with
the easy test to ensure that eval() works.
However, to test the file operations, like "files named moe", I have
