[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





--- Comment #2 from Stefan Pendl <pendl2megabit at yahoo.de>  2009-06-19 08:35:15 ---
(In reply to comment #1)
> 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.
> 

Yes, I am currently using this approach, but I have to change three things,
including the SOFTWARE variable, if WPKG is moved to a different location or to
set up a testing environment, which if overlooked results in serious problems.

> 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.
> 

So could we introduce two new WPKG client settings (check boxes)?
1) Set WPKG_ROOT to the parent folder of wpkg.js
2) Set WPKG_TOOLS to %WPKG_ROOT%\tools

Since we are on the subject, I think most of us use the parent folder of
WPKG_ROOT as the SOFTWARE folder, so this could be another check box in the
WPKG client.

---
Stefan

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