Hi Nicolas, As far as I know you are discouraged to use the freeze/unfreeze commands as of symfony 1.1 (and so also in 1.2). Instead, you are recommended to distribute the symfony libraries in your project using, for instance, svn:externals. More info on how I approach this can be found on my weblog (so that I don't have to explain it here, I'm lazy ;) : http://www.leftontheweb.com/message/Distributing_your_project_with_symfony_embedded
Stefan On Tue, Dec 2, 2008 at 3:34 PM, Nicolas <[EMAIL PROTECTED]> wrote: > > Hello everyone, > > I'm quite new to symfony but i think the freeze/unfreeze task doesn't > work properly in the 1.2 release: > > In the dev environment : > > $ symfony -V > symfony version 1.2.0 (/usr/share/php/symfony) > > $ ls -l web/ > sfPropelPlugin -> ../../../../../usr/share/php/symfony/plugins/ > sfPropelPlugin/web/ > sfProtoculousPlugin -> ../../../../../usr/share/php/symfony/plugins/ > sfProtoculousPlugin/web/ > > which is what is expected. Now freezing the project: > > $ symfony project:freeze /usr/share/php > (...) > Warning: rename(/home/nico/symfonyProjects/SmanageScripts/data/symfony/ > web/sf,/home/nico/symfonyProjects/SmanageScripts/web/sf): No such file > or directory in /usr/share/php/symfony/task/sfFilesystem.class.php on > line 189 >>> plugin Configuring plugin - sfPropelPlugin >>> plugin Configuring plugin - sfProtoculousPlugin >>> plugin Configuring plugin - sfGuardPlugin > > Seemed to have worked and finished correctly, but: > $ ls -l web/ > sfPropelPlugin -> ../../../../../usr/share/php/symfony/plugins/ > sfPropelPlugin/web > sfProtoculousPlugin -> ../../../../../usr/share/php/symfony/plugins/ > sfProtoculousPlugin/web > > The links are not updated, and now unfreeze the project: > $ symfony project:unfreeze > (...) > Warning: unlink(/home/nico/symfonyProjects/SmanageScripts/web/sf): No > such file or directory in /home/nico/symfonyProjects/SmanageScripts/ > lib/symfony/task/sfFilesystem.class.php on line 143 > > Seemed to have worked too, but then: > $ ls -l web/ > sfPropelPlugin -> ../lib/symfony/plugins/sfPropelPlugin/web > sfProtoculousPlugin -> ../lib/symfony/plugins/sfProtoculousPlugin/web > > and now the links point to the libs where the freezed one should be > but the project was just unfreezed... > > imho the tasks just mix the update of the plugins links the other way > around : a ticket was opened for the same bug but it was closed for > RC1 by fabian > > Hope this helps, > Nicolas- > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
