On 03/23/11 09:32, Mark J. Nelson wrote:
It seems to have perfectly expected results.... is this because you
want to blend debug first and then arch later?
Yes.
More generally, I want to not care about ordering. Stripping
pkg.merge.blend means that only the first merge will be blended, and
subsequent merges will not be. So ordering is important. My argument
is that this is nonintuitive behavior: A + B != B + A.
The only way to support this is to make the value of pkg.merge.blend
significant, unless we leave it on the published package (bletch).
Ok...
I see what you're driving at...
pkg.merge.blend needs to have a value; when it matches the
variant being blended it acts and is removed... multiple
may be specified per action.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with Mercurial than with Thunderbird."
"Civilization advances by extending the number of important
operations which we can perform without thinking about them."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
