Hi, If the URI processing solution does not work out for you, there is also the common work around I use for such scenarios: If a file $IN is supposed to be read-only, but $PROGRAM tries to write to it, I typically create a compound rule such as
: $IN |> cp %f tmp && $PROGRAM tmp -o %o && rm -f tmp |> $OUT *Temporary* files that are both read and written to are permitted by tup, so this works. Of course there will be some cost to copying, which may or may not be problematic, depending on the file size of $IN. (Or you can copy it to /tmp, which requires reading the file into memory, but at least not writing to disk.) Regards Neil -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
