Le ven. 8 févr. 2019 à 13:08, Travis Everett <travis.a.ever...@gmail.com> a écrit :
> This doesn't address the portability issue, but I'm not sure I see why you > would need to copy timestamps in two directions? > > I'm just suggesting that you use Doxygen to generate a "scratch" copy that > you never deploy (and could delete immediately after rsyncing) and using a > one-way rsync to another location where you store the "real" copy for > use/deployment/processing/etc. Sphinx would run on the "real" copy, not the > scratch one. > Thanks Travis, I think you're right. I went for a "two-ways" solution because it cost little more code once I opted to sort of "re-implement rsync in Python" instead of using rsync itself. It also saved me changing the doxygen destination which was a bit more convenient for testing and comparing. Then I lost track of this non-requirement :-)
_______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
