Nicolas Chauvet wrote:
The split with vlc-core isn't about binaries vs libraries, but
with
headless/server/core vs wayland/Xorg/display.
… which is a split whose usefulness I doubt. All the applications with
associated library are split into app and app-libs, not app (GUI) and
app-core.
What you suggest is to add libvlc and libvlc-core to vlc and
vlc-core.
Yes, if you want to keep the -core split, we need a 4-way split, I have been
saying that for months.
See how other applications that can be embedded as a library are split,
e.g.:
http://pkgs.fedoraproject.org/cgit/rpms/avogadro.git/tree/avogadro.spec
(avogadro-libs)
http://pkgs.fedoraproject.org/cgit/rpms/marble.git/tree/marble.spec
(marble-widget-qt5)
http://pkgs.fedoraproject.org/cgit/rpms/konsole5.git/tree/konsole5.spec
(konsole5-part)
Even if the main package is small, it still makes sense to not drag in end
user applications as dependencies of other applications.
That's not implemented, and IMO it doesn't worth either. What
would be
the benefit not to rely on vlc itself ?
- not having the vlc desktop file?
- not having vlc binaries ?
- not having the qt4/qt5/skin2 vlc gui interfaces ?
All of the above. A Phonon backend should not drag in a media player UI.
Kaffeine should also not drag in the VLC application that serves the same
purpose and clutters the menu.
I all theses cases, it could be to minimize the dependencies cost
more
than additional size of few unneeded binaries. And speaking about
phonon, you should already have the qt4/qt5 libs.
But dependencies size matters most for embedeed/server use case, not
workstation. So it's doesn't bring any value and just make things more
complex to deal with.
It brings the value of clean packaging and uncluttered menus.
Kevin Kofler