The problem is that cap has to accomodate the lowest common denominator, and not every ls supports -r, or -1.
- Jamis On Tue, Jun 16, 2009 at 1:20 PM, Rob<[email protected]> wrote: > > OK, in the latest release the code is: > _cset(:releases) { capture("ls -xt #{releases_path}").split.reverse } > > which is better, but could be even better as: > _cset(:releases) { capture("ls -1tr #{releases_path}").split } > > In any case, cap _2.5.5_ does the right thing. > > -Rob > > On Jun 16, 1:33 pm, Rob <[email protected]> wrote: >> On a new server that I'm setting up, I've run into a slight problem. I >> have a partition mounted to hold the releases. >> >> Filesystem Size Used Avail Use% Mounted on >> /dev/mapper/code-app 5.3G 329M 4.7G 7% /data/stylepath/ >> releases >> >> in the recipes/deploy.rb, there is: >> >> _cset(:releases) { capture("ls -x # >> {releases_path}").split.sort } >> >> and the name "lost+found" sorts later than the 20090616132111 style >> names and cap tries to run a rake from the lost+found directory. >> >> (As an aside, I don't know why the command is "ls -x ..." it seems >> like "ls -1 ..." would be more intention-revealing.) >> >> Is there any way to override this list to be some like either: >> _cset(:releases) { capture("ls -1 #{releases_path}/[0-9] >> *").split.sort } >> Or: >> _cset(:releases) { (capture("ls -1 #{releases_path}").split - >> ['lost+found']).sort } >> >> -Rob > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
