AFTER ignores named jobs that don't generate a cronstamp

[DNied]

If job Y is waiting on job X (AFTER=X) but job X (ID=X) does not generate a cronstamp (because it's not scheduled via FREQ, but via the "classic" fields), then job Y is never executed.

This is undocumented behaviour (and IMHO counter-intuitive). All jobs named with an ID should probably generate a cronstamp, regardless of the syntax with which they are scheduled.

[Slider-Whistle]

Hey, I think I might be running into this same issue myself. @DNied

* * * * * ID=pullfromnascache FREQ=1h /usr/sbin/emaint sync -a &>/dev/null
@noauto ID=up2date AFTER=pullfromnascache /usr/bin/emerge --update --newuse --changed-use
--deep --keep-going --with-bdeps=y @world --quiet

Should my job on line 2 be running here? I think it follows the workaround you describe, but I'm still not getting any new cronstamps for it. I guess I could combine them into one job with an &&, but that just wouldn't feel right to me.