On Sun, Jun 22, 2014 at 5:34 AM, Freddie Chopin <[email protected]> wrote:
> Hello! > > I guess the main reason to ignore hidden (dot) files and directories is to > ignore .tup folder with the database. But is there a good reason to ignore > ALL such files/directories? Recently there was a discussion about a simple > operation of generating repository hash which is not possible with tup > because this would depend on a file in .git folder... > > If the only reason is to ignore .tup then maybe it would be possible to > change tup to ignore this folder only, not all starting with dot? > > On the other hand - is it really necessary to ignore .tup folder (assuming > that's the reason for this rule)? > > Primarily it was to ignore both .tup and .git - I don't think there's any reason for a sub-process to be using files in .tup, so there's no we don't need to scan & track them. In .git, I think (maybe incorrectly?) that things would be changing as things get put into packs, or stashed, or whatever, that it would cause a lot of spurious rebuilds if you had sub-processes depend on those files. Maybe you can try to disable the ignore-the-dot-folders feature and see if it helps or just makes things annoying :) -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]. For more options, visit https://groups.google.com/d/optout.
