I've just noticed that a few of the symlinks in the Linux poplog
distribution refer to directories starting '/bham/common/'. I think that
explains some of the odd behaviour a few Linux users have noticed (such as
key bindings slightly different to the Sun version).
It'll be easy enough for me to put a tarball together to patch this, but
I'm not sure where the symlinks should link to. The files are:
$poplocal/local/USER.FILES/Poplib/vedfiletypes.p ->
/bham/common/system/templates/user.poplog/Poplib/vedfiletypes.p
$poplocal/local/USER.FILES/Poplib/vedkeys.p ->
/bham/common/system/templates/user.poplog/Poplib/vedkeys.p
$poplocal/local/USER.FILES/dotfiles/dotXdefaults ->
/bham/common/com/packages/poplog/Login/Xdefaults.poplog
$poplocal/local/USER.FILES/dotfiles/dotctwmrc ->
/bham/common/system/templates/user.standard/.ctwmrc
$poplocal/local/com/USER.FILES/Poplib/vedfiletypes.p ->
/bham/common/system/templates/user.poplog/Poplib/vedfiletypes.p
$poplocal/local/com/USER.FILES/Poplib/vedkeys.p ->
/bham/common/system/templates/user.poplog/Poplib/vedkeys.p
$poplocal/local/com/USER.FILES/dotfiles/dotXdefaults ->
/bham/common/com/packages/poplog/Login/Xdefaults.poplog
$poplocal/local/com/USER.FILES/dotfiles/dotctwmrc ->
/bham/common/system/templates/user.standard/.ctwmrc
$poplocal/local/com/login.scripts/user.poplog ->
/bham/common/system/templates/user.poplog
$poplocal/local/com/login.scripts/user.standard ->
/bham/common/system/templates/user.standard
My suggestion would be:
1) Copy Xdefaults.poplog into dotXdefaults
2) Create a directory $poplocal/templates/, with user.* in them
3) Make all of the other links point to their equivalent in
$poplocal/templates
The only problem I can see with this is that it would require a difference
between the true Birmingham set-up and the others - $poplocal/templates
and dotXdefaults would have to be symlinks at Birmingham, but not on the
distributions.
Anyway, can someone tell me to go ahead with the patch like this, or give
me a better/different solution.
- Andrew
|