Re: How to safely build GARNOME-2.10.x
- From: "Joseph E. Sacco, PhD" <joseph_sacco comcast net>
- To: Ivan Noris <noris bgs sk>
- Cc: garnome-list <garnome-list gnome org>
- Subject: Re: How to safely build GARNOME-2.10.x
- Date: Tue, 12 Jul 2005 15:29:52 -0400
There are issues in my mind as to just how automated we would like the
build, install, and setup for the stable GARNOME release to be.
It's easy to imagine a garnome-setup script that is run once by each new
user. It is also easy to get carried away with this idea.
Suppose the build/install "creates" [more likely edits] two scripts
* garnome-session
* garnome-setup
and places these in the $(GARNOME)/bin directory.
The garnome-session script contains the usual environment setup stuff
and ends with a call to $(GARNOME)/bin/gnome-session
The garnome-setup script would be an something with an interactive
dialog that a new user runs once to "check stuff" and create either
xinitrc.garnome or xsession.garnome in the user's home directory. I
would not attempt to automatically edit the user's existing .xnitrc file
or .xsession file. That's just asking for it...
-Joseph
On Tue, 2005-07-12 at 15:01, Ivan Noris wrote:
> Hi Joseph,
>
> > The real problem is only some of the applications that depend upon
> > gstreamer provide intelligent diagnostics messages that suggest running
> > gst-register when the registry appears corrupt.
>
> Maybe the XML file that gst-register produces contains some useful version...
> but anyway, you would need to know current version of gst-register, so running
> it (e.g. with -h or something) would be needed. I don't like it.
>
> > I would opt for putting "run gst-register" in the INSTALL notes.
> > Putting it in the start script should work, but would add 7-10second [on
> > my system] to the startup time.
>
> I know, that's the reason why I didn't even try it. It's too long.
>
> > If there are enough things-to-do like running gst-register, I would be
> > in favor of creating a "garnome-check-prep" script to be run once by
> > each new user.
>
> Well, this looks better. The script could create some dot-file then, to know,
> that it was already run. Checking for this file in garnome-session (if it
> already exists) would not slow the startup-process much.
--
joseph_sacco [at] comcast [dot] net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]