Unfortunantely, a lot of the CCK field adding, updating, removing, etc is tied up in form submission right now. In fact, the content_copy.module import is basically just mocking up drupal forms and submitting them programmatically. This is not to say a CRUD API couldn't be written, just that I've been down that road before, and I it wasn't fruitful. :-( As to importing CCK stuff right here and now: http://cvs.drupal.org/viewcvs/drupal/contributions/modules/crm/crm.install?r... On 5/31/07, adrian rossouw <adrian@bryght.com> wrote:
I was thinking it would be cool if we could have a way for CCK node types to be defined by modules.
The same way that modules can provide default views.
A quick way to do this would be to just have a module that generates a module for node types, generating the .info, and the .install .. and probably a dummy .module.
this could really help with install profiles.