Hi Henrik,
Thanks for your feedback. I think it will be fine, sort of like a "pipe via intermediate variable". As with pipes, it may be tricky to pass the same result to more than one action; can you assign the result to another variable and use it more than once?
I looked into adding a general concept of variable however decided to do without it for now since we never needed such a concept up-to-this point and it added significant amount of work that would not necessary. That said, I made sure that adding variables later on would be possible though I think that if / when we will reach that point we should start looking into using a real language (remember when the first prototypes of p2 used _javascript_?) and also look into other research results of the Mancoosi project that had analyzed the scripts of linux packages and determined that a turing complete language was not necessary for such a task. Naturally all actions needs to either set the result to nothing, or to something meaningful.
Correct. For backward compatibility the ProvisioningAction now returns a default avlue of "NO_VALUE"
Pascal
+1 in general.
- henrik
On Dec 29, 2012, at 3:12, Pascal Rapicault wrote:
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
|
