You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, since version 12 of the parser (commit 341b929), it prints this instead:
$ tup
...
* 1) [0.001s] .
tup error: %e is only valid with a foreach rule for files that have extensions.
-- Path: 'test.txt'
tup error: Error parsing Tupfile line 3
Line was: ': foreach *.txt |> cp %f %o |> %B.$(NAME_%e)'
[ ] 100%
*** tup: 1 job failed.
The text was updated successfully, but these errors were encountered:
sboukortt
changed the title
[Regression] Cannot use %e in output files since parser version 12
[Regression] Cannot use %e in output filenames since parser version 12
Jan 19, 2016
@gittup don't you think it would be wise, to finally create a new release including (but not limited to) this fix? I mean, all the official package managers' stable branches on all linux systems still have this particular bug, because those are still using the almost 3/4 year old 0.7.4! What I'm trying to say is, as a package maintainer myself, it is kind of a pain in the arse, to add a single extra special dependency to all my projects, that is, "one should download and install the current git version of tup, and not the stable one, which is wildly available on one's package manager" -- not to mention, that the latest clone will very likely be in a conflict with the users' current setup, and will drive the package manager's crazy, to say the least. Thanks in advance!
This used to work:
However, since version 12 of the parser (commit 341b929), it prints this instead:
The text was updated successfully, but these errors were encountered: