<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body style="direction: ltr;" bidimailui-charset-is-forced="true"
bidimailui-detected-decoding-type="latin-charset" text="#000000"
bgcolor="#ffffff">
Good point. I think the first decision someone needs to make in this
case is whether they want their content type and fields to depend on
CCK being present. It's possible either way, of course, but a whole
lot more work.<br>
<br>
<blockquote
cite="mid:AANLkTi=xgWpoK=h2JinpLO8zMu=jwaVSdoXHX_X3Db7B@mail.gmail.com"
type="cite">Victor wrote:<br>
<br>
One way to avoid this whole problem would be to adopt an
everything in code process (either through features or leaning
heavily on the installation api module and bulk export modules).
<div><br>
</div>
<div>That way, updates are all like module updates.</div>
<div><br>
</div>
<div>See
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<span class="Apple-style-span" style="color: rgb(68, 68, 68);
font-family: Georgia,'Times New Roman',Times,serif; font-size:
16px; line-height: 24px;"><a moz-do-not-send="true"
href="http://nuvole.org/blog/2010/aug/24/features-based-development-workflow"
style="margin: 0px; border-width: 0px; color: rgb(163, 27,
0); text-decoration: underline;">http://nuvole.org/blog/2010/aug/24/features-based-development-workflow</a></span></div>
<div><font class="Apple-style-span" color="#444444" face="Georgia,
'Times New Roman', Times, serif" size="3"><span
class="Apple-style-span" style="line-height: 24px;"><br>
</span></font></div>
<div>
<div>The technique works whether you use features or not.</div>
<div><br>
</div>
</div>
</blockquote>
</body>
</html>