<br><br><div><span class="gmail_quote">On 8/22/06, <b class="gmail_sendername">Neil Drumm</b> <<a href="mailto:drumm@delocalizedham.com">drumm@delocalizedham.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Nedjo Rogers wrote:<br>> We have the ability to include _install functions in install profiles.<br>> What about updates? We're currently registering the install profile<br>> through variable_set('install_profile'). Should we instead be setting it
<br>> as a row in the system table? That way we could track its schema version<br>> like we do for modules and so invoke e.g. default_update_0() when<br>> update.php is run.<br><br>What updates would install profiles run? My understanding is that they
<br>are only for enabling modules and setting configuration on installation.</blockquote><div><br>Say an install profile ships with a gardened/maintained taxonomy (config). This could be updated centrally over time.<br></div>
<br>Same could be said for "boilerplate" content of various kinds -- shipping with integrated help, etc.<br><br></div>In general...it will allow for versioning. We're really just at the early stages of this...need to get a couple out in the wild. This just "feels" like the right solution...
<br clear="all"><br>-- <br>Boris Mann<br>Vancouver 778-896-2747<br>San Francisco 415-367-3595<br>Skype borismann<br><a href="http://www.bryght.com">http://www.bryght.com</a>