----- Original Message ----- From: "Jeff Turner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Thursday, December 27, 2001 8:56 AM Subject: [OT] Ant-driven update system (Re: Best way to add file to CVS repository?)
> Incidentally, 'diff -N' is not a general, nor cross-platform, solution > to the problem of how to convey updates. Do you know a plattform where cvs is not available? I've even found references to ports to AS/400 and MVS that are in the works. > I'd like to invent one though :) I was thinking along the lines of a > .jar file containing updates, with an Ant script, META-INF/control.xml, > which describes how the contents of the jar must be applied. There are other people inventing replacements for cvs, for example http://subversion.tigris.org which should also work thru firewalls as it uses WebDAV for repository access. > Basically, a jar file that knows what to do with itself. Much like an > RPM or .deb file. Can you deliver *patches* with rpm or deb-packages? I always thought they would always contain the complete package and - maybe - now how to update an older installation if there is one avaialble. But you always need to distribute the whole package, don't you? Okay, but what you are describing is really a system to patch distibuted software, isn't it? Personally, I don't think that a project which aims to be "a Java based build tool" should care about patching your installations. Maybe a task to create such a patch would be nice to have in Ant, but the invention of the complete patch-system goes beyond the target of Ant. Nico -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
