On 03.04.2015 17:23, Spooge wrote:
I added an option to do some debug printing (-v). Can you check the
following?
1. Make sure tup will still run - if you ran the output script it
might mess up the db when tup scans (not sure) because of externally
generated files.
2. Run with -v and save stdout+stderr - this should have "Commands:"
followed by a dump of the internal tree data.
3. If it still doesn't work, can you send me the log and your .tup/db
one more time?
I probably see where's the problem with your project. In here everything
works perfectly well if I generate the script while all the outputs
generated by tup still exist. This sequence works:
1. tup
2. python ~/Downloads/chrome/tup-export-master/tup_export.py script.sh
3. rm -rf output
4. chmod +x script.sh
5. ./script.sh
However - this sequence produces a faulty script which doesn't have any
mkdir calls, has the order wrong and doesn't list any input files for
linker (it's the script that I've sent previously):
1. tup
2. rm -rf output
3. python ~/Downloads/chrome/tup-export-master/tup_export.py script.sh
4. chmod +x script.sh
5. ./script.sh
Is this expected? If it is, then your script should detect that and
report an error. Or at least it should be clearly stated in the help.
Regards,
FCh
--
--
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.
