On Tue, 2017 Mar 28 09:35+0200, Rene Engelhard wrote: > > > > If LibreOffice is installed without Java runtime support, then how > > is the failed installation of Java-based third-party extensions a > > problem? That is exactly what should happen. > > But people out there don't know what their extension is written in and > (often) don't know about java-common or so. Thus the metapackage gets > it in because newbies out there just do apt-get install libreoffice.
That command already pulls in the Java stuff, including lo-java-common, because the metapackage Recommends: packages that require Java (like lo-report-builder). You already solved this problem without Depends: lo-java-common. > Trust me, we have been there various times and thus why a default LO > install *does* install it. It's not that I don't trust you, it is that this "solution" does not help the problem you are describing. If you try an experimental build without that dependency, "apt-get install libreoffice" will install exactly the same set of packages as now.