Takao: > If GDM calls gnome-session directly without dtstart, is it no problem that > Indiana Live Session runs dtstart? > I.e. dtstart can load scripts in /etc/X11/xinit/xinitrc.d and we don't have > to ask installer team any changes?
I think it makes sense to repurpose the dtstart script so that it sources the scripts in /etc/X11/xinit/xinitrc.d and then starts the session. > Now 'dt' might mean DeskTop instead of CDE. That's what 'dt' always meant, I believe. > I noticed one issue. > Previously /usr/dt/config and dtstart were included in SUNWgnome-dtstart in > Indiana. > Now we move dtstart in SUNWdesktop-startup and how do we treat /usr/dt/config > ? Yes, I think it makes sense to move the dtstart script to the SUNWdestkop-startup package. It's now just a shortcut script for starting up the user session by hand. > The current .spec means /usr/dt/config is moved to > SUNWgnome-dtlogin-integration as same as Nevada. Do we deliver > SUNWgnome-dtlogin-integration into > Indiana newly? I think we should avoid delivering SUNWgnome-dtlogin-integration in Indiana. It should only be delivered on systems where CDE login may be used. > Option 1: Deliver both SUNWdesktop-startup and SUNWgnome-dtlogin-integration > in Indiana. > Option 2: Deliver SUNWdesktop-startup only in Indiana and we remove CDE > supports in Indiana. This sounds right, except that Indiana has never supported CDE. I believe on Indiana we were making use of the /usr/dt/config/Xinitrc.jds script. However, this did not mean we ever "supported" CDE in Indiana. We shouldn't need the /usr/dt/config directory anymore on Indiana since the code from Xinitrc.jds has moved into /etc/X11/xinit/xinitrc.d, correct? Instead the new dtstart script should just source /etc/X11/xinit/xinitrc.d and then run the proper session startup program (e.g. gnome-session for GNOME). > Option 3: Deliver both SUNWdesktop-startup and SUNWgnome-dtstart. > SUNWdesktop-startup includes dtstart and xinitrc.d scripts and > SUNWgnome-dtstart > includes /usr/dt/config. Brian
