Message-
From: Upayavira [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 13, 2004 7:34 AM
To: [EMAIL PROTECTED]
Subject: Re: XConfToolTask and more than one patch action per file
Ralph Goers wrote:
I was thinking I would just look at the child nodes of the root. If they
are
all patch
-Original Message-
From: Claas Thiele [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 11:45 PM
To: [EMAIL PROTECTED]
Subject: Re: XConfToolTask and more than one patch action per file
Ralph Goers wrote:
I had thought about doing this in my last update to XConfToolTask, but I
didn't
than one patch action per file
What about:
patches
xconf xpath=/cocoon/blah/ .
node/
/xconf
xconf xpath=/cocoon/blah/xxyy ...
anothernode/
/xconf
xmap xpath=/cocoon/blah/zzz ...
yetanothernode/
/xmap
xlog xpath=/cocoon/blah/yyy ...
somethingelse/
/xlog
than one patch action per file
Ralph Goers wrote:
I had thought about doing this in my last update to XConfToolTask, but I
didn't want to add two features in one patch.
Doing this could actually be pretty easy. Currently, it looks at the root
node and grabs info from it. It would be pretty
Thiele [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 11:45 PM
To: [EMAIL PROTECTED]
Subject: Re: XConfToolTask and more than one patch action per file
Ralph Goers wrote:
I had thought about doing this in my last update to XConfToolTask, but I
didn't want to add two features in one patch
What about:
patches
xconf xpath=/cocoon/blah/ .
node/
/xconf
xconf xpath=/cocoon/blah/xxyy ...
anothernode/
/xconf
xmap xpath=/cocoon/blah/zzz ...
yetanothernode/
/xmap
xlog xpath=/cocoon/blah/yyy ...
somethingelse/
/xlog
/patches
This would allow me to
Ralph Goers wrote:
I had thought about doing this in my last update to XConfToolTask, but I
didn't want to add two features in one patch.
Doing this could actually be pretty easy. Currently, it looks at the root
node and grabs info from it. It would be pretty easy to see if the child
nodes are
Whats the reason for having one patch action per patchfile only?
Using filesets the execution order of the patches is not predictable and
so it is a hell writing more complex patches.
Would it be a good idea having a set of actions in one patchfile like
xupdate has?
Claas
one patch action per file
Whats the reason for having one patch action per patchfile only?
Using filesets the execution order of the patches is not predictable and
so it is a hell writing more complex patches.
Would it be a good idea having a set of actions in one patchfile like
xupdate has
