On 14.01.2011, at 20:18, gordonslondon wrote: > I think only files that exists in both bundles should be overwritten, the > others are kept (current behavior). > > Maybe i don't understand what you want to say. > Do you mean that the logic should be done when calling assets helper instead > of assets:install command ?
vi src/Application/FOS/UserBundle/Resources/public/foo.txt -> set content to 'foo' touch src/Application/FOS/UserBundle/Resources/public/c.png vi src/Bundle/FOS/UserBundle/Resources/public/foo.txt -> set content to 'dong dong' touch src/Bundle/FOS/UserBundle/Resources/public/b.png php app/main/console_dev assets:install --symlink web gives me: web/bundles/user/foo.txt (content 'dong dong foo') web/bundles/user/b.png With the approach Jordi described (http://groups.google.com/group/symfony-devs/msg/33490139cabc890f) it would "effectively" (*) be like: web/bundles/user/foo.txt (content 'foo') web/bundles/user/b.png web/bundles/user/c.png Plus adding any file to either place would immediately be available when using the symlink option. (*) I am saying effectively because in reality the files would be in different locations and the "magic" would be done via the asset helpers. Though I would limit this to just to just symlink mode. When using copy imho everything should be merged into one dir. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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.com/group/symfony-devs?hl=en
