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
"implicit *" behavior went away in 0.4.x #187
Comments
Will confirm and fix this. Thanks for reporting! |
I can see a very valid argument for insisting that includes be explicit. But perhaps others, like me, were scripting some stuff that relied on the former behavior. |
So here's what I can do: If the 'source' is "dir" and you specify -C, it will imply that "." is the thing you want to input. The old behavior of:
Note the '.' at the end. I'll see about making this work. |
Sounds good. |
Here's what works for me now:
|
Looks good! |
and chdir (-C) is set. Fixes issue #187 - Abort if there's no package name known.
This fix will appear in the next release of fpm, hopefully today :) |
and chdir (-C) is set. Fixes issue jordansissel#187 - Abort if there's no package name known.
and chdir (-C) is set. Fixes issue jordansissel#187 - Abort if there's no package name known.
and chdir (-C) is set. Fixes issue #187 - Abort if there's no package name known.
and chdir (-C) is set. Fixes issue #187 - Abort if there's no package name known.
0.3.10: "Created /tmp/foo-1.0.x86_64.rpm"
0.4.3: "You need to pass additional command arguments so that I know what you want to build packages from."
The text was updated successfully, but these errors were encountered: