[wpkg-users] [Bug 260] Feature Request - WPKG to automatically create variables

[bugzilla-daemon at bugzilla.wpkg.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |r.meier at wpkg.org
         Resolution|                            |WONTFIX

--- Comment #1 from Rainer Meier <r.meier at wpkg.org>  ---
Hi Peter,

Also here (much like your request in bug 259). I see the largest drawback in
having to support such things for many different platforms (OS/Architecture
etc).

Also here I think it would be much more helpful to provide a couple of helpers
to do the job.

Your first example of a common pattern has the issue that it contains the
"SomeSoftware" folder which WPKG does not know and therefore is unable to
create. The second example just deals with the fact that %DESKTOP% is on a
different location on Windows XP and on Windows Vista and newer.

Also here WPKG would be made platform-dependent if it starts to implement such
automatic variables. However there is a better solution for it I believe. Use
template scripts.

I am going to attach a script to this bug report which you can perfectly use
for this purpose. I am using a all to evaluateFolders.cmd in all installer
scripts which require access to such common folders. It currently supports
Windows 2000 and newer with English and German locale. And yes, this is another
issue I would not like having to deal with the main wpkg.js code:
Language-specific settings. I want to avoid having to update wpkg.js just
because someone is using it on a system with some locale setting which has
never been used by anybody else. The result will be very frequent releases with
adaptations to special environments.

I mean we could provide such services on request; but definitely only as part
of some commercial agreement.

In respect to your bug 259 request where I suggested to use simple scripts you
could very easily use the evaluateFolders.cmd helper to get correct paths.

e.g.

<install cmd='%SOFTWARE%\tools\copyToDesktop.cmd
"%SOFTWARE%\software\software.lnk"' />

Then the "copyToDesktop.cmd" script could be simply made up of the following
lines:

---
@echo off

call "%SOFTWARE%\tools\evaluateFolders.cmd"
copy /Y "%~1" "%DESKTOP%" > NUL

---

That's all required to copy a file to the desktop.


Alternatively I repeat again that you could use XSLT in order to include common
variables like the DESKTOP variables from an external XML file. So you would
have to write only one single XML file which defines the "DESKTOP" variable for
all the systems you intend to support.

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