https://bugs.documentfoundation.org/show_bug.cgi?id=161300

--- Comment #5 from N.P. <[email protected]> ---
> Can you please try to install libavahi and see if it fixes it?

"Our security policy prohibits the installation of avahi."

I thought I could overcome this by compiling avahi, and just adding the
directory containing the library to my $LD_LIBRARY_PATH, but after wasting
hours trying to build avahi, I completely understand why people won't use it.

I will indulge myself a brief (off-topic) mini-rant describing my travails. 
I never intended to *install* avahi (that would require adding news users to
the system, and installing several dependencies not present on the system -
something I can't do). I thought I could at least get it to compile, though.
The documentation seems hopelessly out of date (it mentions gtk+2, but doesn't
mention a required dependency that I assume the developers added recently). The
configure script represents a nightmare. If it didn't find something optional
("can't find Mono C# compiler"), it failed instead of continuing without that
feature. I eventually got the configure script to complete by adding five
--disable-feature options to it. The attempted compilation produced more
warnings than I have ever seen before while compiling a piece of software. The
build eventually aborted because the developers forgot to include a script in
the tarball (the latest release occurred more than four years ago, and while
they developers added that script to the tree last year, they have not released
an updated tarball). After tracking down this issue, I downloaded that script
and placed it in the proper directory of the source tree, but alas, the compile
still failed, but for a different reason (cannot stat some file supposedly
created during the build). At that point, I abandoned trying to compile avahi
to create libavahi (and would describe the avahi soucre code as something that
rhymes with "map"). Maybe it works adequately when compiled and installed, but
I have no desire to engage with it further.

As a final comment, I will say (agreeing with some comments in bug 119408) that
LibreOffice should not *require* any networking tools to function.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to