On 11.09.2012 23:23, Michael C. Robinson wrote:
> I installed Hunspell, but when it came to installing a dictionary I
> found the link to be broken...
>
Uh, Hunspell is really simple. Just install it with --prefix=/usr and
put dictionaries in /usr/share/hunspell. Firefox/Xulrunner already
provides en_US hunspell dictionaries in
/usr/lib/{firefox,xulrunner}-x.y.z/dictionaries ... Also, hunspell uses
myspell dictionaries too. That's how I got croatian dictionary for hunspell.
> Trying to compile enchant which detects Hunspell, the compile bombs on
> can not find hunspell.cxx.
>
I think you should start new thread for that and post exact output.
> Background for people confused about my goals concerning Gnome:
>
> As far as installing Gnome in a non standard location, I am curious
> why it is so hard to make that work?
> I found that even putting the odd library locations in /etc/ld.so.conf
> that things still didn't work.
> I started over so that /usr/gnome is being used as a build directory
> and package repository instead of
> an installation target.
>
We had a discussion on that when I wanted to pull in GNOME 3.4. The main
problem is not just PATH an LD_LIBRARY_PATH (or entry in
/etc/ld.so.conf) ... There are several things needed for Desktop,
expecially for GNOME. For example, D-Bus, GLib and Polkit are installed
into /usr and expect their rules into /usr and/or /etc hierarchy, not
somewhere else. By pointing gnome prefix somewhere else you'd need to
either install mentioned packages into same prefix and force their use
(no clue how) or symlink system locations to the correct gnome prefix
locations which won't make GNOME that isolated. GLib gio module location
is hardcoded at GLIB_PREFIX/lib/gio/modules and if installed anywhere
else, it would make Gvfs, GConf and DConf not working. Among other
things there might be a problems with icons, since lot of icons get
installed in $PREFIX/share/icons/hicolor, but only hicolor-icon-theme
provides necesary files for gtk-update-icon-cache to address those icons
as present, otherwise you'd end without most of icons on your system.
Also, XDG_USER_DIRS would have to be set to point to PREFIX/share (it's
by default /usr/share and maybe /usr/local/share). And at last, do not
try to use SYSCONFDIR as anything else than /etc. Using anything else
can break GConf and DConf databases, as well as startup files located in
/etc/xdg/autostart by default. Setting variable could work for internal
desktop, but it would break GDM badly.
And among other things you'd need to look for correct PAM prefix for PAM
modules and config files, pkcs11 modules, Telepathy modules and such.
> I hope the Gnome people realize that Gnome is getting to be like
> Windows 98 was back in the day where everyone screamed about Internet
> Explorer being integrated when they wanted Netscape instead. I
> realize that evolution usually comes with Gnome, but I don't need
> evolution on a system intended for backup/restoration of other
> systems. My suspicion that the book doesn't document well what can be
> left out when building Gnome seems to
> be correct. I know for a fact that evolution itself can be
> uninstalled in Fedora without hobbling Gnome.
Please note, Evolution IS NOT Evolution Data Server. Evolution Data
Server is just a set of *libraries* or shared objects if you like.
Google for libraries if you don't understand. These contain the
functions *required* to integrate all components of GNOME Desktop
together (hence the desktop) without needing whole application for that.
> Even wireless tools and Network Manager are listed as requirements for
> Gnome, I want to leave both out for
> two reasons. Reason one is that Network Manager could muck with the
> wired network interface and break the NFS root. Reason two is that I
> don't intend to support wireless interfaces in a backup/restoration
> environment. Wireless links are slow and unstable, not ideal for NFS
> root.
>
Same as for E-D-S. Wireless Tools are not just "Wireless Tools". They
also contain shared library and development headers which are *required*
for wireless functionality in NetworkManager. GNOME has became so much
*touch stuff* orientated that wireless seems to be essential. Please
remember that you are not only user there and most of users today
(especially laptop users) want to use wireless.
> I hope people don't really think I'm complaining, I'm just noticing
> more than anything how many dependencies
> there are for full blown Gnome and how difficult it is to determine if
> any of them can be safely dropped.
>
Required dependencies are really required to build. Recommended
dependencies are not required to build the package, but you can miss
some functionality at runtime or even some other package would fail to
build because the package x is missing functionality from package y. As
I said earlier, all GNOME components are integrated closely together so
sometimes it is impossible to determine what or what not do you really
need. I hope I've written great instructions that can be used to build
full GNOME flawlessly and also that it can work flawlessly as every
GNOME guy would expect it. That also includes GNOME Shell, which pulls
lot of dependencies.
I could have made a mistake at some package and put x as required or
recommended when it could be safely disabled without harming anyone, but
GNOME itself is so big and one can get lost.
> I've been pursuing a Gnome installation for a few different reasons.
> Education, I need to understand what is in a Linux system because I
> want to become Linux certified. User friendliness, I'm putting this
> network system together for people who don't feel comfortable at the
> command line that will benefit from having it as a sort of fallback
> when their local systems break. Reason three involves Gnome specific
> applications that might make sense. For a pdf reader, the Gnome
> specific choices may be preferable.
Evince can be safely installed without GNOME components. I think that
instructions already show that.
There are Gnome specific game
> demos I'd like to throw in as a nice touch, though I have to figure
> out how to compile 32 bit libs for them.
I think that I replied at this one. You need multilib setup which LFS
does not support. CLFS is way to go for that.
I'm thinking that
> LibreOffice may require Gnome or KDE. I want graphical logins, user
> friendliness idea, where GDM seems to be the way to go.
>
LibreOffice can use GNOME or KDE components just for integration. That
does not make them required.
> I'm thinking I may want to start in runlevel 3 text mode and have a
> post login script that gives a menu allowing selection of Runlevel 4,
> which will trigger GDM. Another option is to put type /sbin/telinit 4
> to get graphical logins in /etc/motd. I have fluxbox and twm right
> now, but fluxbox has to be started
> manually.
>
Your distro, your rules. Just please do note if you break anything while
slightly modifying the book instructions which were already tested to
work, you get to keep all the pieces.
If everything else fails, there are Xfce and LXDE and even KDE as
alternatives ...
No offense.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
