Closed (won't fix)
Project:
Drush System Manager
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Aug 2009 at 13:25 UTC
Updated:
31 Jan 2012 at 15:34 UTC
any chance you can submit the views commands to views project? i am willing to take the cck commands into drush project since they are in core for d7. let me know what you think. also, let me know how troubled i should be by the project page's statement "Module is not fully tested and needs more work. Especially the import of the the views and content types."
Comments
Comment #1
moshe weitzman commentedmy understanding is that features module offers cck and views export and creates a "features module" to house them. thats probably the way to go.
Comment #2
moshe weitzman commentedactually, features has proven a bit brittle for this.
Comment #3
clemens.tolboomI think that movings things to where they belong is a good strategy :)
I prefer to get paid for my efforts unless it's a developers itch. And this project is more of the latter.
Intersecting drush and drush_sm we share variables
- drush: set / get / del but no list or report
- drush_sm : set / get / list/report but no del
The above keeps the itch :p Could we add the variables list and report to drush?
I think moving the cck part to drush would be a good idea. The drush team has more time to spend. At least I hope.
Moving the views part to views is a great idea. But for that I need some pointers how to make it version agnostic.
Comment #4
clemens.tolboomBoth drush and features are matured a lot.