[Radiant] Standard Rake Install/Uninstall Tasks for Extensions

[Sean Cribbs]

I've kind of kept out of this discussion so far, but there does exist an 
'update' task that is generated for new extensions since 0.6.3 (I 
believe).  It copies files from the extension's public folder to the 
project/instance public folder.  However, there is no reverse operation 
for it currently.  I imagine the tasks might look something like this 
(cleanup would be the reverse of update):

task :install => [:migrate, :update]

task :uninstall => :cleanup do
  ENV['VERSION'] = 0
  migrate
end

Sean

Todd Willey wrote:
> On Jan 10, 2008 8:01 PM, John Long <me at johnwlong.com> wrote:
>   
>> On 1/10/08, Mario T. Lanza <mlanza at comcast.net> wrote:
>>     
>>> Added a tiny section called "Standard Rake Tasks" to:
>>> http://wiki.radiantcms.org/Creating_Radiant_Extensions
>>>       
>
> Why not put those tasks in the generated Rakefile and just have them
> do nothing by default?
>
> We could also make assets/{javascripts,stylesheets,images} directories
> and have the install task copy files from those directories to their
> counterparts in public by default (but should not overwrite something
> already there, probably).
>
> -todd[1]
>
>   
>> Perhaps that should be put at the bottom in an Additional Notes
>> section? Or even better truly work it into the tutorial by adding an
>> code examples and screenshots.
>>
>> --
>> John Long
>> http://wiseheartdesign.com
>>
>> _______________________________________________
>> Radiant mailing list
>> Post:   Radiant at lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>>     
> _______________________________________________
> Radiant mailing list
> Post:   Radiant at lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
>