On Mon, Sep 28, 2015 at 3:18 PM, Freddie Chopin <[email protected]> wrote:
> Hello! > > Is there any specific reason why multiple output groups are forbidden? I > just > wanted to use many output groups to group the outputs in a hierarchy (so > that > I could have groups of files created in a/ folder, which would be equal to > the > sum of a/1/ and a/2/ groups, which in turn would be equal to the sum of > a/1/x, > a/1/y and a/2/x/ and a/2/y/ groups respectively) and tup told me that's an > error: > Hi Freddie! I don't think there are any major technical reasons why it couldn't be implemented. There was an issue filed on github a while back for this that has some more details: https://github.com/gittup/tup/issues/166 > > > tup error: Multiple output groups detected: ... > > Groups are the closest thing to global variables (but with some > limitations) > and sometimes having a global variable (that can transfer information > between > Tupfiles) is really necessary if you want the build to be more "automatic". > For example the thing I had in mind would work as an automatic collector of > outputs (but with hierarchical structure represented by the path of groups) > and this can be replaced with explicitly listing all the subdirectories > (and > sub-subdirectories and sub-sub-subdirectories and ...), but that's just > stupid > to list all of that manually... > > Yeah, they can be handy :). Part of me thinks that we could just use groups for inputs/outputs and not list any files manually. Though we'd also have to fix the explicit-listing-of-output-files issue for that to work. -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.
