On Wed, May 19, 2021 at 10:58 AM Sam Sam <[email protected]> wrote: > Hi Mike, > > You got my use case perfectly well, I’m trying to avoid re-running some > time consuming tasks by storing their targets on a distant volume. > After checking out my pipeline source code (including the tup file) from a > version system, I perform a tup init and an rsync to fetch some of these > large targets; and I was wondering if tup could continue from here. > > I definitely understand that recognising those pre-existing target would > defeat tup core features, so I’ll just stick with some more standard use > cases :) > > (Still just for fun, I’ll try to rsync the generated files and the tup > database, I’ll see how it goes) >
I believe that syncing the database as well should work, so long as you make sure mtimes on generated files are kept, which rsync with -a should do. Is there a reason you are wanting to re-create new .tup directories frequently rather than just re-using the same one each time? > > @mike: In all cases, thanks a lot for your work, I got several build > systems running under tup after just browsing the documentation a couple of > times, that’s really a well thought software. > > Thanks for the feedback! That is refreshing to hear :) -Mike -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/tup-users/CA%2B6x0LX8gnkSgVLrQd4q7XUi4TX-3tKpU2iP70htugL3AB5SSA%40mail.gmail.com.
