Hi Glenn,

Glenn Lagasse wrote:
>>
>> Glenn Lagasse wrote:
>>     
>>>> - VMC Manifest: It would be useful to specify whether these are new
>>>> tags? Or replacement tags to existing things? and which section in
>>>> the DC manifest these tags will appear.  Also, what happened to all
>>>> the existing content in DC manifests?  Additionally, for DC, the
>>>> order in which the finalizer scripts are listed is very important.
>>>> So, please list the order of the finalizer scripts (new and
>>>> existing), and the order in which they will be executed.  It would
>>>> be much more clear if you can include the manifest the VMC project
>>>> will use as reference.
>>>>         
>>> Well, we don't have a manifest yet (it's a task to create one).  At the
>>> moment, it's likely to be very stripped down from the other DC manifests
>>> we currently have and consist mostly of just a finalizer section.  We
>>> can definitely clarify what order the finalizer scripts will be run in.
>>> And as for tags, it looks like we may not use tags and just specify
>>> values as arguments to the finalizer scripts.
>>>
>>>       
>> IMO, if a value will only be used by 1 finalizer script, it is easiest to
>> pass it in as an argument to the script.  If a value is needed by multiple
>> scripts, it is more error-prone to pass it in as arguments to
>> different scripts.
>> It is probably better to define it "somewhere appropriate"
>> in the manifest once, and then, just have the finalizer scripts query it.
>>     
>
> I'm not sure I agree.  As it is, every finalizer script is passed in 5
> arguments right off the bat whether the script needs them or not
> (manifest server socket for instance).  While I think we will pass some
> values amongst multiple scripts, I don't think that's necessarily a bad
> thing.
>
>   
The 5 arguments that's always passed to each scripts are not
specified in the manifest.  It's "computed" by DC based
on the "build area" value in the manifest.  We have to
pass those 5 arguments now because there's currently
no way for the DC app to "communicate" with the finalizer scripts.
When the unified engine work is done, the DC app will be able
to get rid of the 5 arguments and pass information a "better" way.

--Karen

Reply via email to