[vlc-devel] [PATCH 00/14] Move VLM implementation to a module

[Rémi Denis-Courmont]

Hello,

This is ridiculous. You are again totally oit of line. By now, your recurrent attempts at attacking and occasionally defaming me jere feel to me nothing but pitifully pathological.

Who moved GnuTLS out of the core, as well as gcrypt (before Rafaël brought it back in)? Me.
Who de-duplicated FFmpeg the first time after the plugin was split by another dev? Me.

I don't think thay I ever made a blanket rejection of moving the update code to a module in any and all forms. If I had, I'm sure you'd have quoted it already.

All I did was reject one approach in a specific patchset from François. And as I most likely mentioned back then already, the only way to actually truly de-duplicate gcrypt in VLC installs is to build it as a dynamic library. That's because it's also used by contribs. And the one person who objects to that approach is... you.

So there you go.

Le 17 septembre 2020 14:21:58 GMT+03:00, Jean-Baptiste Kempf <jb at videolan.org> a écrit :
>On Wed, 16 Sep 2020, at 17:07, Rémi Denis-Courmont wrote:
>> Le keskiviikkona 16. syyskuuta 2020, 11.23.50 EEST Romain Vimont a
>écrit :
>> > Hi Rémi,
>> > 
>> > On Tue, Sep 15, 2020 at 09:10:16PM +0300, Rémi Denis-Courmont
>wrote:
>> > > Le tiistaina 15. syyskuuta 2020, 20.37.32 EEST Romain Vimont a
>écrit :
>> > > > This removes a lot of VLM code (including parsing) from
>libvlccore.
>> > > 
>> > > What is the actual point of this?
>> > 
>> > The idea was to lighten and simplify libvlc core (the complexity
>being
>> > moved to the VLM module), and not load the VLM code in memory when
>VLM
>> > is not used (which is often the case).
>> 
>> If you want to de-bloat libvlccore, move the gcrypt-based update code
>to a 
>> module. With static linking that's orders of magnitude larger than
>any other 
>> core component.
>
>Yes, and the changes around gcrypt were blocked by your objections, in
>a similar way that this current discussion.
>
>> Moving code to a module marginally increases disk and memory use due
>to module 
>> overhead. If the module is not used, it might marginally decrease
>memory use, 
>> but probably won't. And even if it does, it's a coin toss whether
>it'll 
>> actually offset the increase.
>
>It's also to load less parsing-code by default.
>
>-- 
>Jean-Baptiste Kempf -  President
>+33 672 704 734
>_______________________________________________
>vlc-devel mailing list
>To unsubscribe or modify your subscription options:
>https://mailman.videolan.org/listinfo/vlc-devel

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20200917/a67ccfde/attachment.html>