On 03/18/10 16:26, Mark J. Nelson wrote:
Howdy--
A question in #onnv jogged my memory this afternoon, and got me thinking
about merge.py.
I cc'd Bart and James because I know they've both done some
brainstorming in this area.
Is anybody actively working on this? I was kind of wondering if
time-of-merge was the best time to solve packaging problems like
SUNWrmod and SUNWonbld. If we could tag an action with a special
variant value that would tell merge.py "always include this object,"
instead of having it be strict about mapping source repositories to a
single variant value, then it seems like we could do at least the
special cases we've already considered.
This could work but it certainly raises some interesting error
conditions; if variant A has an action marked
"always-include-on-merge=true" but variant B is not marked that way,
things are
tricky. In addition, I anticipate multiple merges (debug/non-debug,
sparc/x86) so perhaps
"include-on-merge=variant.arch" would be a better approach.
Actions to be included on both debug/non-debug and arch* merges
would need both tags...
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
