http://bugzilla.wpkg.org/show_bug.cgi?id=260
--- Comment #3 from Peter Hoeg peterh...@gmail.com ---
I hope it's ok to re-open this FR after so long, but I thought the case wasn't
completely closed.
Basically, I think that adding the complexity to WPKG itself is a good idea.
There are 3 places
http://bugzilla.wpkg.org/show_bug.cgi?id=260
--- Comment #4 from Rainer Meier r.me...@wpkg.org ---
I still believe that option 1 (hard-coding such variables in WPKG) is the worst
out of all. I am not even saying that it would be hard to implement, but not
everything which can be implemented does
http://bugzilla.wpkg.org/show_bug.cgi?id=260
--- Comment #5 from Rainer Meier r.me...@wpkg.org ---
OK, I am back with one additional response.
In fact I did not want to force-close the issue without re-thinking about a
proper solution. So there was one more potential improvement coming to my
http://bugzilla.wpkg.org/show_bug.cgi?id=260
--- Comment #6 from Peter Hoeg peterh...@gmail.com ---
This is truly stellar, thanks Rainer, that solves it nicely.
One tiny request now - I would imagine that most people are happy with using
config.xml with its defaults, so could we possible have
http://bugzilla.wpkg.org/show_bug.cgi?id=260
Rainer Meier r.me...@wpkg.org changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
http://bugzilla.wpkg.org/show_bug.cgi?id=260
--- Comment #2 from Rainer Meier r.me...@wpkg.org ---
Created attachment 229
-- http://bugzilla.wpkg.org/attachment.cgi?id=229
Evaluate common variables
Script which evaluates common variables such as %DESKTOP%, %STARTMENU%,
%STARTMENU_PROGRAMS%
