devassistant incorrectly handles yaml anchors

[msrb]

Following yaml configuration works fine:

files:
  license: &license
    source: python/lib/LICENSE
...
- cl: cp *license .

I believe that following configuration should also work, but it doesn't:

files:
  MODIFICATION: &license
    source: python/lib/LICENSE
...
 - cl: cp *license .

devassistant fails with:

INFO - Checking for presence of python...
INFO - Found python-2.7.5-1.fc20.x86_64
INFO - Checking for presence of python-setuptools...
INFO - Found python-setuptools-0.6.36-1.fc20.noarch
INFO - Creating library project LIB1 in . ...
ERROR - cp: cannot stat ‘*license’: No such file or directory

[bkabrda]

This seems to be a problem, since there is no way to get the the anchor name from parsed yaml (unless we heavily modify pyyaml parsing output, which doesn't seem to be a good idea).
I'll leave this bug open; for now, we just have to name the file and the anchor the same, I'm afraid (hopefully that doesn't hurt to much...)

[bkabrda]

To clarify this a bit:

• when there's a *somefile on its own somewhere, it's treated during Yaml parsing as a reference, e.g. foo: *bar
• when there's a reference that is a part of a string, e.g. cl_i: cp *foo . then it's substituted by DevAssistant during runtime

Since DevAssistant can't access anchor names, but only the specified files mapping names (MODIFICATION in the above example). Since this is not fixable reasonably, I'll document this and close this bug. Anyone is free to reopen and fix, if there is a nice fix for this.