Hi,
nanoc opts for a non-destructive approach, which means that stray files will remain in the output directory. Backwards compatibility is one of the reasons for this: storing files not managed by nanoc in the output directory used to be a recommended approach, and changing nanoc's behaviour to delete stray files would result in data loss.
The nanoc site has a rake task for removing stray files. Check out http://projects.stoneship.org/hg/sites-nanoc/file/ca4aa376dcb7/tasks/clean.rake. Alternatively, you could delete the output/ directory and recompile, but this would probably result in unnecessary recompiles. Come to think of it, a built-in command that does exactly this would probably be useful.
Cheers
Denis
Op 6 mei 2011 06:57 schreef "auxbuss" <aux...@gmail.com> het volgende:
--
You received this message because you are subscribed to the nanoc discusssion group.
To post to this group, send email to na...@googlegroups.com
To unsubscribe from this group, send email to nanoc+un...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/nanoc