[development] Update.php re-design
nabil at gobrighttree.com
Wed Mar 4 15:35:24 UTC 2009
On Wed, 2009-03-04 at 10:47 +1100, Gordon Heydon wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> And since I created that issue I have had working code for Drupal 5
> and above.
umm... ok? It's cool that you got working for all three. Soon enough
there are going to be 4.
> The only time the update.php script is changed in during the major
> Drupal updates. ie from Drupal 5 to drupal 6. All the other changes
> are in the install files.
Just because a problem happens only once in a while doesn't mean that it
isn't a problem
> Drupal already have an update api, which is a part of the install
> files attached to every module. My goal with the issue I raised is to
> create a minimize the common code between the 2 and allow the updates
> to be done from either method.
Yes I agree with you that the goal and I hope that we can maybe work
together on this. The current problems that I see are three:
1. Major upgrades, i.e from drupal 5 to 6 to 7 (to 8?).
2. Even though your script works, a lot of energy is required to
re-create or change it.
3. Duplicate code between the two update scripts (web and cli) but an
update.inc could resolve this.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
> -----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.drupal.org/pipermail/development/attachments/20090304/2aa4eb05/attachment.pgp
More information about the development