[wpkg-users] [Bug 273] New: Per user install support

bugzilla-daemon at bugzilla.wpkg.org bugzilla-daemon at bugzilla.wpkg.org
Tue May 15 22:47:06 CEST 2012


           Summary: Per user install support
           Product: WPKG
           Version: other
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: wpkg.js
        AssignedTo: mangoo at wpkg.org
        ReportedBy: k.e.jones at brighton.ac.uk
         QAContact: wpkg-users at lists.wpkg.org

I wasn't sure if this thought was on the roadmap already. I suspect it is  or
I've missed something along the journey. Please ignore this if it's a waste of
thinking time :-)

 I've now started seeing smaller software developers adapt their products to be
installed by non-privileged users to cope with Windows 7's security model.

 For instance, I now have a piece of software that is basically an MSAccess
.accde file installed into the users %APPDATA% folder and not the machine's
one. Desktop shortcuts are added to the user's profile to point to that file
which circumvents the need for a per-machine install.

 As far as I can see WPKG still doesn't formally support per-user installs.I
think it's definately robust enough to handle that with trivial changes and
some subtle thinking :-)

 I would like to suggest the implementation of a /context switch with values
"machine" or "user". The /context:"machine" being assumed as the default value
and keeping WPKG compatible with current setups. The /context:"user" being an
option you'd add if you run WPKG.JS as a user logon script.

 In theory, when supplied with the "user" value WPKG would only need to change
two things;

 a) redirect the WPKG.XML path to the user's %appdata% folder.
 b) switch host matching to use the currently logged on user instead of the
host machine/IP/etc.

 I appreciate that this trivialises many things but I can't actually see many
coding hurdles. I can't actually see many operational issues either. In theory,
it should all work already it just boils down to how people implement their
WPKG setups :-)

 I have an awful feeling that I'm missing something... surely it can't be that
easy? There might be some performance issues but WPKG really is self-healing so
it could actually survive very well.

 Am I being awfully stupid?


Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the wpkg-users mailing list