<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="https://build2be.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>build2be/com/e - installing</title>
 <link>https://build2be.com/category/installing</link>
 <description></description>
 <language>en</language>
<item>
 <title>module dependency management</title>
 <link>https://build2be.com/content/module-dependency-management</link>
 <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;p&gt;I don&#039;t like the idea that dependencies are not handled in a unified way. By that I mean that both module.inc and update.php code is written to handle module status. There should be a central library handling their dependencies. When we handle this in a unified way installing a big project like ubercart is easy.&lt;/p&gt;
&lt;p&gt;When installing/enabling a module it is important to know what this module is dependent of. Ie uc_cart is dependent of uc_order. See ie &lt;a href=&quot;http://build2be.com/sites/build2be.com/files/ubercart.neato.png&quot;&gt;http://build2be.com/sites/build2be.com/files/ubercart.neato.png&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Mon, 03 Mar 2008 08:55:21 +0000</pubDate>
 <dc:creator>clemens</dc:creator>
 <guid isPermaLink="false">17 at https://build2be.com</guid>
 <comments>https://build2be.com/content/module-dependency-management#comments</comments>
</item>
</channel>
</rss>
