[wpkg-users] [Bug 262] Wrong variable apply order

bugzilla-daemon at bugzilla.wpkg.org bugzilla-daemon at bugzilla.wpkg.org
Fri Jan 13 16:02:24 CET 2012


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

--- Comment #4 from Rainer Meier <r.meier at wpkg.org>  ---
OK. I perfectly understand your input. I do declare full compatibility with
earlier versions since I always tried to keep compatibility in the code.
Variable expansion however was pretty special regarding the fact that it was
not clearly specified how variables got expanded in version 1.2.x. Depending on
package installation order the results might have changed. So the complete
system of variable handling was re-checked.

I do also fully understand that the evaluation order now was changed (which
admittedly breaks the 100% compatibility rule). Actually both ways of
evaluating variables have advantages and disadvantages. WPKG also allows to do
any package implementation with either evaluation order (see conditional
variables).

So personally I am even fine if the order is reverted to WPKG 1.2.x order.

Options are:
- Host
- Profile
- Package

or

- Package
- Profile
- Host

The first one makes sure variables defined in the package are really set as
specified in the package and not just accidentally all packages get
re-installed since somebody used %VERSION% in the revision attribute and then
defined VERSION on profile level. But it does not allow overriding of variables
which are not designed to be overridden (e.g. by condition).

The second option allows overriding of package variables easily but might
result in unexpected effects if a profile or host defined variables which are
used by a package.


As I said I am open to discuss this; the changes to WPKG would be pretty
minimal I would say. Is anybody else using heavy variable overriding?

@Stefan: I think you might use it. Which variable overriding policy would you
opt for? ;)

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