On 9/5/06, Christopher D. Malon <[EMAIL PROTECTED]> wrote:
In summary, the basic pattern would be: (a) smokeserv-client sends both .html and .yml of smoke
I really really want this feature. I've even added this to Pugs' TASKS file.
(b) If smokeserv-server gets .yml, it checks out the t/ directory for that revision, and
To be honest, at this moment I don't quite care about checking out t/. Instead I just hope the new smoke server can make the tests.yml with largest rev number available somewhere in the index page. ;-)
(c) smokeserv-server runs smartlinks.pl on the .yml with that t/ directory and indexes it.
I don't know if the smoke server has checked out smartlinks.pl like feather. My current plan is to run smartlinks.pl on feather and render the synopses using the latest version of pugs smoke results. I admit your approach is much saner, but apparently needs much more work. :) I also share a lot of your questions. Hopefully the maintainer of the current smoke server (ingy or nothingmuch?) can give some guide here. :) Cheers, Agent
