Separate user data from program logic about subuser HOT 3 CLOSED

Why not add a small: conf-subuser file in the subuser base directory

simples option: using a 'conf-subuser.py' and import it when executing subuser (which should stay in the subuser base directory /bin or so

programsThatCanBeInstalledPath = "/blabla/bla"
subuser-binPath = "/blabla/bla"

or use a 'conf-subuser.json' and use json to handle it

from subuser.

I think that the proper approach is to add optional json files to the users home dir and the /etc/ directory which would specify alternate locations for things. Like:

~/.subuser/conf.json

and

/etc/subuser/conf.json

The key thing is that these config files have to be optional, so that the run-in-place variety of subuser still works without hitch.

from subuser.

subuser/logic/subuserCommands/subuserlib/paths.py will look for paths in the following order:

First it will look for paths in ~/.subuser/paths.json then /etc/subuser/paths.json then $SUBUSERDIR/paths.json. This will be a partial fallback method, so that ~/.subuser/paths.json and /etc/subuser/paths.json may contain some but not all of the paths. $SUBUSERDIR/paths.json must contain all paths though as it defines the paths. When expanding these paths the ENV_VAR $SUBUSER must be set appropriately.

Run os.path.expandvars(path) on the paths.

$SUBUSER/paths.json will look like:

{
  "repositories" : ["$SUBUSERDIR/programsThatCanBeInstalled"],
  "bin" : "$SUBUSERDIR/bin",
  "installed-programs.json" : "$SUBUSERDIR/installed-programs.json",
  "user-set-permissions-dir" : "$SUBUSERDIR/permissions/",
  "program-home-dirs-dir" : "$SUBUSERDIR/homes/"
}

paths.json will be documented the same way permissions.json is documented.

Once this is done, #12 (comment) will be fixed.

from subuser.