On17 Mar 2020 17:17:37 +0100, Pieter van Oostrum <[email protected]
<mailto:[email protected]>> wrote:
>
> Date: Tue,
> From: Pieter van Oostrum <[email protected]
> <mailto:[email protected]>>
> To: [email protected]
> <mailto:[email protected]>
> Subject: Re: macports-users Digest, Vol 163, Issue 12
> Message-ID: <[email protected]
> <mailto:[email protected]>>
> Content-Type: text/plain
>
> Murray Eisenberg <[email protected]
> <mailto:[email protected]>> writes:
>
>> I did that: used mode 755 for directories, mode 644 for files there.
>>
>> Still, same error Unable to execute port: Could not open file:
>> /Users/murray/macports/myports/kde/
>> okular/Portfile
>>
>> Did you get this to work with your own version of a port already included in
>> MacPorts?
>
> Yes, I do this regularly. Never had a problem.
> My working mode is: I have a clone of the git repository, but for the ports I
> am working on, I make a copy of the Portfile and other relevant files in a
> shadow directory, but only for those ports.
>
> But 'could not open file' sounds like a protection issue.
> What happens when you execute the shell command?
>
> sudo cat /Users/murray/macports/myports/kde/okular/Portfile
>
> By the way, another way is to go to the directory
> /Users/murray/macports/myports/kde/okular
>
> and execute the command 'sudo port install' (i.e. without port name). It
> should install the port in that directory.
> --
Command "sudo cat /Users/murray/macports/myports/kde/okular/Portfile" _does_
type out the file contents
However, cd to that okulr directory and executing “sudo port install” there
once again gives the same error "Unable to execute port: Could not open file:
/Users/murray/macports/myports/kde/okular/Portfile”.
cdNote that I have:
$ ls -l Portfile
-rw-r--r--@ 1 murray staff 2296 Mar 16 15:18 Portfile
Moreover, I get the same error if I execute “chmod a+wx Portfile”.
---
Murray Eisenberg [email protected]
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667 Mobile (413)-427-5334
