How to get around MacPorts assuming that Exit code: 1 is a failure?
Eric Gallager
egall at gwmail.gwu.edu
Sat Feb 8 18:46:06 PST 2014
I had to escape the brackets, but after that, it worked. Thanks!
On Sat, Feb 8, 2014 at 9:23 PM, Joshua Root <jmr at macports.org> wrote:
> On 2014-2-9 12:22 , Eric Gallager wrote:
> > I am working on a Portfile from which I want to call the `unifdef`
> > command. The manpage for `unifdef` says: "Exit status is 0 if output is
> > exact copy of input, 1 if not, 2 if trouble." The whole reason I am
> > running `unifdef` is to change the output, so I /want/ it to return 1.
> > However, when I put this in my Portfile, it interprets this as a
> > failure. Is there any way that I can get around this?
>
> unifdef || [ $? -ne 2 ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140208/1565a80a/attachment.html>
More information about the macports-dev
mailing list