Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Regression] Cannot use %e in output filenames since parser version 12 #262

Closed
sboukortt opened this issue Jan 18, 2016 · 3 comments
Closed

Comments

@sboukortt
Copy link

This used to work:

NAME_txt = out

: foreach *.txt |> cp %f %o |> %B.$(NAME_%e)
$ tup
...
 1) [0.008s] cp test.txt test.out
 [ ] 100%
[ tup ] [0.748s] Updated.

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.
@sboukortt 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 gittup closed this as completed in 311994d Feb 19, 2016
@sboukortt
Copy link
Author

Thank you very much. :)

@petervaro
Copy link

petervaro commented Aug 21, 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!

@gittup
Copy link
Owner

gittup commented Aug 26, 2016

Yep, sorry for the delay! This should be in v0.7.5 now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants