[meego-packaging] Dropping yaml

[Pertti Kellomäki]

On 04/01/2011 02:17 PM, Boudra Fathi (Nokia-MS/Helsinki) wrote:
> That's an upstream bug: the tests (binaries, architecture dependent) shouldn't be shipped into /usr/share directory (architecture-independent data).
>    
I happen to agree, but I also know that fixing it is way way down in the 
priority list of the upstream. So...
> nothing to do with spectacle/yaml capabilities.
>    
... does IMO gloss over some details. Moving things around in a post 
install step is something that is trivial to do in a spec file, but 
AFAIK is not possible in a yaml file. Whether it is advisable is another 
matter, but "you can do everything in yaml" is a very different 
proposition from "you can do everything you should be able to do 
according to our policy in yaml".

The fact that yaml needs a hidden escape mechanism to spec is a strong 
indication that yaml is not in fact sufficiently expressive. If it were, 
there would be no need for an escape mechanism, right? Another strong 
indication is that in order to submit stuff to the build system, I in 
fact need to run a manual build step beforehand. If the options were to 
either submit a yaml file or a spec file, then the story would be 
consistent: there is the recommended way of using yaml, and a deprecated 
legacy way of using spec files. But the fact that you need submit *both* 
sends quite a mixed signal.
-- 
Pertti