Comment # 28
on bug 10737
from Guy Harris
(In reply to yuri from comment #26)
> Once you install everything into custom directory, you should also run
> desktop environment from that same custom directory (maybe as chroot), and
> it will find them.
Whether the people who complained to Jeff about that would be happy with such a
solution is another matter. (And chroot is a bit of a sledgehammer; if it lets
you get at stuff outside the custom directory, that's a bug, but you're
probably going to want to, for example, open up capture files outside that
custom directory.)
> But in general passing --prefix=/usr/some/place/ should create all
> directories, including icons, under that dir. This is the responsibility of
> the caller to pass the right directory.
I agree - and that's what we're currently doing (and what I changed Makefile.am
to do with the icon/.desktop/MIME-stuff files, along with moving the
installation of the files to "make install").
Sadly, the whole "path argument variable" notion, introduced lo these many
decades ago with $PATH, and followed by $MANPATH and $LD_LIBRARY_PATH and
$XFILESEARCHPATH and $XDG_DATA_DIRS and so on, doesn't work all that well with
installing stuff in unusual places - you end up having to update those things
manually. It works even less well with the otherwise-somewhat-nice
self-contained application notion, as per earlier comments.
So it ends up being the responsibility of the *user* to make that work, at
least when installing stuff in a location not in the various path variables.
You are receiving this mail because:
- You are watching all bug changes.