in reply to unable to make manifest with symlinks

What are you symlinking to? Something located within the distribution somewhere?

If it's outside of the distribution it'll be useless to others anyhow, so perhaps add the symlink to the MANIFEST.SKIP file (just create it if it doesn't exist within your distribution's root.

Replies are listed 'Best First'.
Re^2: unable to make manifest with symlinks
by mvsjes2 (Initiate) on Oct 23, 2019 at 19:35 UTC
    It's symlinking to other dirs within the same dist. I'm just symlinking to a couple of 'lib' dirs to perl modules so my test files won't have to 'use lib "$FindBin::RealBin/../../../../../../../whatever". I have a symlink so if I move stuff around within the tests I can just update one symlink and the tests will continue to resolve the use statements properly. It's a convenience thing, I can work around it, but I'm puzzled why I'd run into this problem in the first place.
[reply]

      Might I ask the reasoning behind doing things this way?

      In no way do I mean disrespect, but this has the "X-Y Problem" phenomenon written all over it. As someone who was also once a first-time CPAN contributor (always seeking ways to do ingenious things at that), there are sometimes more efficient ways of doing things we might not have thought of yet.

      I've had a look at your Github repo, and it looks sane, except you've got extra stuff in t/ directory which looks a bit odd. Could you explain your reasoning behind why you've done things this way?

      Perhaps instead of helping fix a symlink problem (which, by the number of responses doesn't seem like it's gaining traction), we could assist with easing your directory layout situation, possibly with automation using the build system or even the tests themselves.

      -stevieb

[reply]
[d/l]
        Thanks for the advice. It will be easy to remove the symlinks and clean up the directory structure. I've been working pretty much exclusively on linux for so long that I've developed a bit of tunnel vision and assumed "every o/s supports symlinks", so was just a bit puzzled why I seemed to be the only one in the universe that had run into this problem. Google was not very helpful in this particular case.
[reply]

In Section Seekers of Perl Wisdom