in reply to Re^9: Issues with pp and Tk
in thread Issues with pp and Tk

"I don't really see how either of those searches results in anything useful for the OP. "

Obviously context is key, this is true for any kind of search. OP knows they are dealing with ActiveState and Perl, adding either of those two words finds what is required, ActiveState documentation and so fourth.

"but those ppd files don't contain any info regarding the destination of the files."

They contain a list of files which will be installed, OP could have searched their file system to find all instance of these files, thus providing them with the information they require, the path to the AS version of pp. Alternatively they could make life easier on themselves and take the advice given the last time the posted about module installation woes (and earlier in this thread), setup a sane environment, which would have prevented the whole issue.

Replies are listed 'Best First'.
Re^11: Issues with pp and Tk
by syphilis (Archbishop) on Oct 20, 2017 at 13:20 UTC
    OP knows they are dealing with ActiveState and Perl, adding either of those two words finds what is required

    Oh, yes - searching for "ActiveState ppd file" produces much more promising results.

    They contain a list of files which will be installed

    Are you sure about that ?
    The ppd files that I create for MS Windows ppm packages certainly don't contain any such info, and I'm of the opinion (without actually having gone to the trouble of recently checking) that the ppd files provided (for Windows) by ActiveState are also devoid of such info.
    Admittedly, we are talking about Macs here - and I have to confess that I don't know what the ppd files for that OS look like. I see no reason to think that the Mac ppd files would be significantly different ... but , it *is* Macs after all, and that makes speculation a very risky business indeed.

    Cheers,
    Rob

      You're right, this is a valid point. The build log linked to does, the file generated does not. The ppd file actually points to a tar file which when extracted shows the files of which PPM will shuffle around the system to.. wherever...

      I don't believe MacOS will be any different in this respect. I'll fix that, I'd have been better off just linking to pp.. Regardless, I still believe simply addressing the root cause of the problem is a saner course of action, rather than trying to spoon feed an impractical work around because the former requires some effort on OPs part.