Added multicore processing and "only update changed files" feature #12
Conversation
| optpart = optpart " " opts[i] | ||
| } | ||
| printf "find \"%s\" -type f \\( %s \\) -exec zod-%s \"%s\" \"%s\" \"%s\" {} \\;", proj, optpart, phase, zod_lib, proj, target | ||
| printf "find \"%s\" -type f -cnewer \"%s/.zod/state\" \\( %s \\) -print0 | xargs -0 -P %s -I {} zod-%s \"%s\" \"%s\" \"%s\" {} \\;", |
There was a problem hiding this comment.
The -P option to xargs is not POSIX standardized. It is not supported by busybox, however it is supported by GNU findutils, by FreeBSD, OpenBSD, macOS, and illumos.
There was a problem hiding this comment.
The -cnewer option to find is not POSIX standardized. Maybe it can be replaced by -newer, which is POSIX standardized, however it compares the modification time of the files, rather than their change time, to the modification time of ./zod/state. I am not exactly sure how that would make a difference.
There was a problem hiding this comment.
I don't use any of this any more, but I was not sure if zodiac consciously aspires towards POSIX compliance?
There was a problem hiding this comment.
I don't use any of this any more, but I was not sure if zodiac consciously aspires towards POSIX compliance?
To be honest, I do not know either! I don't think it is stated anywhere. But there have been people trying to use "zodiac" with busybox before (see #13), so some people might care.
|
gandaro ***@***.***> writes:
@gandaro commented on this pull request.
> @@ -26,5 +32,6 @@ END {
for (i = 0; i < length(opts); i++) {
optpart = optpart " " opts[i]
}
- printf "find \"%s\" -type f \\( %s \\) -exec zod-%s \"%s\" \"%s\" \"%s\" {} \\;", proj, optpart, phase, zod_lib, proj, target
+ printf "find \"%s\" -type f -cnewer \"%s/.zod/state\" \\( %s \\) -print0 | xargs -0 -P %s -I {} zod-%s \"%s\" \"%s\" \"%s\" {} \\;",
> I don't use any of this any more, but I was not sure if zodiac consciously aspires towards POSIX compliance?
To be honest, I do not know either! I don't think it is stated
anywhere. But there have been people trying to use "zodiac" with
busybox before (see #13), so some
people might care.
As I mentioned, I don't use any of this any more, and I don't @nuex is
either. But on the off-chance that this might get merged, feel free to
suggest changes that I can attach to this PR.
|
2 participants
The title pretty much says it. I implemented these two features because the markdown client I'm using (pandoc) can be pretty slow from time to time, so I'd rather not that all every file is re-rendered all the time. Multiprocessing is practically a
make -jNripoff, but currently it just defaults to the number of cores, ifnprocis found, otherwise it just runs everything sequentially.If you have any problem with any of these changed, feel free to tell me, because to my knowledge, zodiac would be the only simple web-framework to support these features with the amount of flexibility offered, and I guess that others would also appropriate it.