[wpkg-users] [Bug 162] Expose the folder containing wpkg.js as an environment variable

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=162


Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |r.meier at wpkg.org




--- Comment #1 from Rainer Meier <r.meier at wpkg.org>  2009-06-18 20:44:43 ---
Actually I still don't have too much trust in the way WSH sets environment.

In addition WPKG client already supports setting any variable you like. If you
don't use WPKG client then wpkg.js is typically run from a cmd script which can
set variables too.

Most applications I know use some *_ROOT variable - but they do not set them.

Usually I don't like to implement things which bring potential problems...
Modifying the environment is currently optional (if no variables are used the
environment is never touched) and "exposing" a special variable makes
environment modification mandatory (if something fails, WPKG will fail
completely).
In addition some users might use WPKG_ROOT already. And we already had a
discussion on the tools folder where it was agreed that it makes more sense to
set a TOOLS variable within WPKG client.


Well, I agree that it would be technically feasible but for sure it would offer
redundant functionality. So I ask here the opinion of other persons using WPKG.

Would you like that WPKG exposes its root directory using a variable? If yes,
how should this variable be named?
And more precisely: For which purpose you would like to use this variable?

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