Am 26.01.2012 22:12, schrieb Rainer Meier:
So I have reverted it (while keeping the implementation which clearly
defines expansion order now). Results are available on SVN. WPKG version
1.3.1-RC2. See entire discussion in
<http://bugzilla.wpkg.org/show_bug.cgi?id=262>.
Moreover I've implemented checks to allow checking for empty/undefined
variables. So one could still prevent package/host to overwrite a
package variable if required.
I hope this clarifies the situation.
Rainer,
If I remember correctly the variable overwrite order was first mentioned
by a user who was relying on the current overwrite order.
With this change, this user is now facing the same problem, but in the
opposite way.
Wouldn't it be possible to control the overwrite order by a
configuration option?
--
Stefan P.
Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
