| |||||||||||||
Day: GNOME OSDay: GNOME OSPosted Aug 9, 2012 13:53 UTC (Thu) by etienne (subscriber, #25256)In reply to: Day: GNOME OS by slashdot Parent article: Day: GNOME OS
Maybe simpler would be to install in a new directory and "play" with $PATH (or other environment variable) so that shells started before the install see only the previous version and shell started after the update see only the newer version?
(Log in to post comments)
Day: GNOME OS Posted Aug 10, 2012 8:18 UTC (Fri) by nix (subscriber, #2304) [Link]
My old uni did something like this. It was fiercely annoying because it made it *impossible* to upgrade anything without logging out. (Not as annoying as having to reboot to upgrade, but nearly as much.)
Far better to symlink the new things into place in some shared tree. (Of course, symlinks have slight annoying semantic changes, so a few pieces of software need adaptation to this, though maniac stow and graft users like me have already done it for most stuff. If this was really Plan 9, we could just bind-mount everything into place in your per-user /bin, and have a command that refreshed all your /bin mounts when you wanted them refreshed, flash-updating you to the latest goodies but only when you wanted it.)
Day: GNOME OS Posted Aug 10, 2012 9:20 UTC (Fri) by etienne (subscriber, #25256) [Link]
It should be possible to open a new xterm and get newly installed applications in that process group, but I do agree you cannot run the new applications from the global menu without logging out - unless there is a way to "refresh menus".
|
|||||||||||||