cros_workon: store cros_workon state outside of /build

cros_workon: store cros_workon state outside of /build

This solves the problem of cros_workon list of packages being clobbered
by a new setup_board.

BUG=5641
TEST=Verified all cases work correctly.

1. Verified that a pre-existing list of workon packages continues to work.
2. Verified that the package.unmask symlink is created correctly.
3. Verified that a new package can be worked on.
4. Verified that an existing package continues to be worked on.

Change-Id: I566ac898ac4f74bdd5beb532c1ef0f70d4c02cec

[zbehan, 2010-08-25 23:56:28]

http://codereview.chromium.org/3151039/diff/1/2
File cros_workon (right):

http://codereview.chromium.org/3151039/diff/1/2#newcode77
cros_workon:77: die "ln -s ${UNMASK_FILE} ${KEYWORDS_FILE}"
Why not both to WORKON_FILE?

[Mandeep Singh Baines, 2010-08-26 00:18:15]

Fixed. PTAL.

zbehan@chromium.org (zbehan@chromium.org) wrote:
> 
> http://codereview.chromium.org/3151039/diff/1/2
> File cros_workon (right):
> 
> http://codereview.chromium.org/3151039/diff/1/2#newcode77
> cros_workon:77: die "ln -s ${UNMASK_FILE} ${KEYWORDS_FILE}"
> Why not both to WORKON_FILE?
> 

OK. Works either way but I've changed to WORKON_FILE.

> http://codereview.chromium.org/3151039/show

[zbehan, 2010-08-26 00:19:06]

I know it works either way, but I don't see why chain symlinking should be the
way. ;)

LGTM!

On 2010/08/26 00:18:15, Mandeep Singh Baines wrote:
> Fixed. PTAL.
> 
> mailto:zbehan@chromium.org (mailto:zbehan@chromium.org) wrote:
> > 
> > http://codereview.chromium.org/3151039/diff/1/2
> > File cros_workon (right):
> > 
> > http://codereview.chromium.org/3151039/diff/1/2#newcode77
> > cros_workon:77: die "ln -s ${UNMASK_FILE} ${KEYWORDS_FILE}"
> > Why not both to WORKON_FILE?
> > 
> 
> OK. Works either way but I've changed to WORKON_FILE.
> 
> > http://codereview.chromium.org/3151039/show
>