Hi all, I’m experimenting with tup, with an eye towards using it to build our code at work. From the material on <http://gittup.org/tup/>, it looks like it heads in what I would consider the right direction for a build system. I hope that I can get it all the way in that direction, either by clever crafting of tupfiles or possibly by adding features to tup itself.
Along those lines, I have a few suggestions for improving the documentation: • The install direction for OS X are out-of-date and don’t work. To install on OS X 10.11 “El Capitan” I had to instead do the following: $ brew cask install osxfuse $ brew install tup • It could be clearer that FUSE is required. FUSE is only mentioned in the OS X part of the main page, and then only as part of the install directions. The manual page <http://gittup.org/tup/manual.html> only mentions it in prose once, talking about the generate command. This might make tup a non-starter for projects that cannot use FUSE for whatever reason, and it would be nice to have that info up-front. (This is probably not a huge thing, but I’m grumpy that the homebrew osxfuse recommends/requires a reboot in order to install. Yeah, OK, apparently I could have gotten away without a reboot <http://osxbook.com/blog/2009/03/02/why-macfuse-installation-recommends-a-reboot/>, but whatever.) I hope these suggestions are received well; if so, I will doubtless have more as I experiment. If things go well, I might even submit more detailed documentation, such as guides on how to perform useful but tricky build tasks. Harold -- -- 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.
