update.php uses the batch api I believe. It would be brilliant if the whole batch api could be run in CLI mode rather than just update.php. Good luck.<div><br></div><div>Stew<br><br><div class="gmail_quote">2009/3/2 Nabil Alsharif <span dir="ltr"><<a href="mailto:nabil@gobrighttree.com">nabil@gobrighttree.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Great. This is going to be my first contribution to drupal and I don't<br>
know what the process for submitting such changes is. Do I open an issue<br>
and attach patches? Or do I have to sign up for a cvs account and commit<br>
via cvs?<br>
<br>
Would it be better to submit (patches or commit) partial but working<br>
changes, or should I wait until it's all done and then submit one big<br>
change?<br>
<div><div></div><div class="Wj3C7c"><br>
On Mon, 2009-03-02 at 10:22 -0500, Moshe Weitzman wrote:<br>
> This makes sense, and I encourage you and others to proceed. There is<br>
> no good reason it has not been done so far.<br>
><br>
> On Mon, Mar 2, 2009 at 10:24 AM, Nabil Alsharif <<a href="mailto:nabil@gobrighttree.com">nabil@gobrighttree.com</a>> wrote:<br>
> > There seems to be a couple of projects that are trying to make<br>
> > update.php command line friendly, non of which seem to be going that<br>
> > well:<br>
> > <a href="http://drupal.org/node/194107" target="_blank">http://drupal.org/node/194107</a><br>
> > <a href="http://acquia.com/blog/drupal-cli-utils" target="_blank">http://acquia.com/blog/drupal-cli-utils</a><br>
> ><br>
> > The issue that I see is that update.php is tightly coupled with the UI.<br>
> > What I would like to do is pull the functions that preform the updates<br>
> > out of update.php so that it would be possible to have a different UIs<br>
> > to modules (Web interface, cli). There are two main reasons I would like<br>
> > to do this:<br>
> > 1. It would make the projects mentioned above much easier to implement.<br>
> > 2. The projects mentioned above have there own implementation of<br>
> > update.php that is independent of that way drupal updates the modules.<br>
> ><br>
> > I hope to endup with something along the lines of update.inc that holds<br>
> > the function for preforming the updates (i.e get_updates, do_update,<br>
> > db_add_column.. etc) and update.php that has the current UI for<br>
> > updates.<br>
> ><br>
> > Is there any reason that this hasn't been done before? More importantly<br>
> > does any one have any good reason to not separate preforming the updates<br>
> > from the UI?<br>
> ><br>
> > --<br>
> > ----------------------------------<br>
> > Nabil Alsharif<br>
> > Bright Tree<br>
> > 573-499-1244<br>
> ><br>
> > This message is for the designated recipient only and may contain<br>
> > privileged, proprietary, or otherwise private information. If you have<br>
> > received it in error, please notify the sender immediately and delete<br>
> > the original. Any other use of the email by you is prohibited. Please<br>
> > consider the environment before printing this email or its<br>
> > attachment(s).<br>
> ><br>
</div></div></blockquote></div><br></div>