#5311: libreoffice-4.3.0
-------------------------+--------------------------
Reporter: fo | Owner: blfs-book@…
Type: enhancement | Status: new
Priority: normal | Milestone: future
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------
Comment (by Krejzi):
Next time use mailing list for stuff like this, because it has nothing to
do with the ticket.
1. By default, LO was installed in /usr before I left. Why? There is no
point installing it anywhere else because *everything* is contained in
/usr/lib/libreoffice which can be moved around if needed, even to /opt
making it possible to revert to an older version when needed. The stuff
installed in /usr/bin and /usr/share are symlinks and files *required* to
be there so desktops and stuff like that can find them. If you use /opt,
you'd have to symlink icons, desktop files, mime data and app data to /usr
so it can be found properly, which leaves out only binaries from
PREFIX/bin. You have to add them in the path, and they are symlinks to
../lib/libreoffice/blah. Not worth the effort in my oppinion.
2. GNOME can be installed in /opt, but you have to install some stuff
other than from GNOME section in /opt too, namely D-Bus, Polkit, etc. As
those are by default installed in /usr and I didn't want to add duplicate
packages, it was easier to switch everything to /usr. I still accept any
patches that make it possible for GNOME to install in /opt, using as few
hacks/workarounds not appealing to my eyes as possible.
Christopher used jhbuild, and jhbuild builds D-Bus and installs it into
chosen prefix, yet he couldn't start GDM because D-Bus misbehaved when
installed like that. I have no clue why as I never used jhbuild for that
kind of stuff. Not to mention that jhbuild builds everything from git,
removes possibilities of listing optional, recommended deps and stuff like
that.
Note that with KDE5 (Frameworks and Workspaces) it was rather easy to
support installing into /opt and I even use that setup for myself.
3. As for Qt, the instructions still offer installation to /usr and /opt.
The "new" instructions back then broke support for installing both Qt's
into /usr, which worked perfectly fine before then. BLFS systemd
instructions are adjusted to give an user the possibility to install both
Qt's into /usr, /opt, /hell or anywhere else without having to use hacks
not appealing to my eyes to switch paths just because upstream solution
(yes, qtchooser is developed by Qt developers) wasn't understood. The
reason of why I quit because someone who had absolutely no clue about what
was being done ended up changing the instructions, reverting my work
because he thought he knew better (a common disagreement around here) but
haven't had the idea what the packages did in the first place.
You and me were there, think about recent colord disagreement, just add
"breaking stuff" to the list.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/5311#comment:38>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
