crosutils/make_factory_package.sh: Support relative path

crosutils/make_factory_package.sh: Support relative path

Since there's a pushd call when building images, we have to first retrieve
the complete (full/absolute) path of target disk image.

BUG=chromium-os:10706
TEST=make_factory_package.sh \
     --factory ../build/images/x86-mario/latest/factory_image.bin \
     --release ../build/images/x86-mario/latest/chromiumos_image.bin \
     --diskimg blah_relative.bin

Change-Id: I02e2edb0f76b724337a82dd400297877681bc338

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=c584cf0

[Nick Sanders, 2011-01-13 06:54:07]

http://codereview.chromium.org/6244003/diff/1/make_factory_package.sh
File make_factory_package.sh (right):

http://codereview.chromium.org/6244003/diff/1/make_factory_package.sh#newcode89
make_factory_package.sh:89: local outdev="$(readlink -f "$FLAGS_diskimg")"
I don't think this will work. The issue is not symlinks but the fact that we
change directories during the script.

ls -1 $(pwd)/build_packages

may work

[Hung-Te, 2011-01-13 07:05:50]

http://codereview.chromium.org/6244003/diff/1/make_factory_package.sh
File make_factory_package.sh (right):

http://codereview.chromium.org/6244003/diff/1/make_factory_package.sh#newcode89
make_factory_package.sh:89: local outdev="$(readlink -f "$FLAGS_diskimg")"
On 2011/01/13 06:54:08, Nick Sanders wrote:
> I don't think this will work. The issue is not 
> symlinks but the fact that we change directories
  Right, but readlink -f reports full path.

> ls -1 $(pwd)/build_packages may work 
  I think readlink -f is more reliable then the result of ls.
  Check the rest of scripts in src/scripts - they all use readlink -f.

[Nick Sanders, 2011-01-13 07:28:14]

>   Right, but readlink -f reports full path.

Ah, you're right. 

LGTM