<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>remove me plz<BR><BR>
<DIV><FONT color=#000000><STRONG>Yosry SHADY </STRONG></FONT><BR></DIV><BR><BR>
<HR id=stopSpelling>
> From: jpetso@gmx.at<BR>> To: development@drupal.org<BR>> Date: Sun, 7 Sep 2008 18:07:45 +0200<BR>> Subject: Re: [development] CCK field modules maintainers - D6 upgrade path<BR>> <BR>> On Saturday 06 September 2008, Yves Chedemois wrote:<BR>> > To all CCK field modules maintainers :<BR>> > please read http://drupal.org/node/304813<BR>> <BR>> It would make a lot of sense to also have this in the handbook, at <BR>> http://drupal.org/node/191796<BR>> <BR>> Of course, with inter-dependent module stacks getting popular, the nifty <BR>> solution would be a solution in Drupal core, like, say,<BR>> <BR>> mymodule.install:<BR>> ...<BR>> /**<BR>> * Implementation of hook_update_dependencies().<BR>> * Not necessary to implement if this module's update functions do not<BR>> * depend on other module's updates.<BR>> */<BR>> function mymodule_update_dependencies() {<BR>> return array(<BR>> 6000 => array(<BR>> 'content' => 6000, // needs at least CCK 6.x<BR>> 'filefield' => 6301, // and filefield-6.x-3.1 (made up the update no.)<BR>> ),<BR>> );<BR>> }<BR>> ...<BR>> <BR>> Those upgrade dependencies are (still?) so much of an edge case that a lot of <BR>> module developers are apt to ignore them, while with a centralized framework <BR>> it would be easy to implement, with updates being less error prone. Plus <BR>> instead of aborting the whole process like in the above CCK note, those <BR>> updates could run correctly in one go.<BR>> <BR>> Seems easy enough, but I don't exactly feel strong enough about that idea to <BR>> implement it :P<BR>> <BR><br /><hr />Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! <a href='http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us' target='_new'>Try it!</a></body>
</html>