"implicit *" behavior went away in 0.4.x

[astrostl]

cd /tmp
mkdir -p foo/etc
mkdir -p foo/usr/bin
echo > foo/etc/foo.conf
echo > foo/usr/bin/foo
fpm -s dir -t rpm -n foo -v 1.0 -C /tmp/foo

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."

[jordansissel]

Will confirm and fix this. Thanks for reporting!

[astrostl]

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.

[jordansissel]

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:

fpm -s dir -t rpm -n foo -v 1.0 -C /tmp/foo should be the same as fpm -s dir -t rpm -n foo -v 1.0 -C /tmp/foo .

Note the '.' at the end.

I'll see about making this work.

[astrostl]

Sounds good.

[jordansissel]

Here's what works for me now:

% ls /tmp/a
hello

% ruby bin/fpm -s dir -t rpm -n hello -C /tmp/a
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.U1TS3b
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.dThG0R
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.EO1YXx
Processing files: hello-1.0-1.x86_64
Wrote: /tmp/package-rpm-build20120330-21999-wn4d41/RPMS/x86_64/hello-1.0-1.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.OwteYT
Created rpm {"path":"hello-1.0-1.x86_64.rpm"}

% rpm -qlp hello-1.0-1.x86_64.rpm              
/hello

[astrostl]

Looks good!

[jordansissel]

This fix will appear in the next release of fpm, hopefully today :)