On 07/27/2012 11:27 AM, Darrell Anderson wrote:
I want to ensure we have 3.5.12/3.5.11/3.5.10 users covered. I have tested both scripts against a 3.5.10 profile and I am content the scripts wrok well. Yet I can't conceive of all corner cases. Thus far, you're the only additional test case where we can unravel any bugs unless some others volunteer too. If you can keep a copy of that 3.5.12 profile safely stored then we can keep testing. But we also need to determine whether the problem you describe is the profile or the system menus.
I'll get a longer answer later. I'll work with the conversion script and see if we can tease out where the issue is. On Arch, you have XDG_CONFIG_DIRS=/etc/xdg:/opt/trinity/etc/xdg. It is set from:
/etc/profile.d/xorg.sh /etc/profile.d/trinity.sh
Hmm, I wonder how the interplay between these two scripts could impact the menu generation? e.g.:
~/bld/david/opt> cat /etc/profile.d/xorg.sh export XDG_DATA_HOME=$HOME/.local/share export XDG_CONFIG_HOME=$HOME/.config export XDG_CACHE_HOME=$HOME/.cache
if [ -z $XDG_DATA_DIRS ]; then export XDG_DATA_DIRS=/usr/local/share/:/usr/share/ else export XDG_DATA_DIRS=/usr/local/share/:/usr/share/:$XDG_DATA_DIRS fi
if [ -z $XDG_CONFIG_DIRS ]; then export XDG_CONFIG_DIRS=/etc/xdg else export XDG_CONFIG_DIRS=/etc/xdg:$XDG_CONFIG_DIRS fi
~/bld/david/opt> cat /etc/profile.d/trinity.sh export TDEDIR=/opt/trinity export TDEDIRS=$TDEDIR export PATH=$PATH:$TDEDIR/bin export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:$TDEDIR/lib/pkgconfig if [ ! -z $XDG_DATA_DIRS ]; then export XDG_DATA_DIRS=$XDG_DATA_DIRS:$TDEDIR/share else export XDG_DATA_DIRS=$TDEDIR/share fi if [ ! -z $XDG_CONFIG_DIRS ]; then export XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$TDEDIR/etc/xdg else export XDG_CONFIG_DIRS=$TDEDIR/etc/xdg
It looks like this shouldn't be an issue as long as the migration scripts are not called until after the /etc/profile.d/trinity.sh script is run (should be run on X start. However, when I install packages, I install from runlevel 3, so I'm not sure if the environment from either is set when the packages are installed/upgraded. I know this isn't an issue for R14->R14 updates, but the 3.5.12 -> R14 update done in runlevel 3 would not have XDG_CONFIG_DIRS set, but it would if run from runlevel 5.
Will have more time later. I'll also do a cheat sheet for the 3.5.13-sru build and pass that along.