Bug#755154: vlc cache gen should happen at runtime, not buildtime

Rémi Denis-Courmont remi at remlab.net
Fri Aug 22 07:38:51 UTC 2014


Le 2014-08-22 10:31, Harald Sitter a écrit :
> All that being said perhaps the more interesting bit is why exactly
> VLC thinks the cache is invalid to begin with. In particular
> considering we only have one build that builds with all plugins we
> have packaged and there are no third party plugins in any package
> anywhere ever. So the cache should always have a superset of what is
> available on a system.

Changed file name, file size, or file modification time.

>>> I fail to see how exactly the additions could make the maintainer
>>> scripts fail to be honest, other than having a broken cache-gen 
>>> which
>>> surely is the sign of a much deeper problem that should not have
>>> gotten beyond build time to begin with.
>>
>>
>> Experience has shown that changes to certain libraries causes the 
>> cache
>> generation to crash, and the maintainers of those libraries do not 
>> test
>> against VLC before uploading to Debian. I mean glib, gobject, Qt, 
>> GL, libav
>> to name the obvious ones...
>
> How does that work? Wouldn't that also defunct the plugins 
> themselves?

VLC would probably crash too, but a crashing program is not as bad and 
as likely to be reported as a crashing installation procedure.

-- 
Rémi Denis-Courmont



More information about the pkg-multimedia-maintainers mailing list