Updating frameworks stored in subversion?

  • Hi,

    Is there a proper method for updating a framework stored within
    subversion?  I recently pulled my common code out into a framework,
    then added the framework back into my project.

    Now, if I make changes to the framework and recopy over the new
    framework, I get 155005 errors because the .svn file becomes confused
    with the new folder.

    Am I just doing this all wrong?  Should I not put the framework bundle
    into subversion in my project?

    Thanks for any help or pointers to the correct docs.

    Brian
  • On Apr 27, 2008, at 12:39 PM, Brian Krisler wrote:

    > Is there a proper method for updating a framework stored within
    > subversion?  I recently pulled my common code out into a framework,
    > then added the framework back into my project.
    >
    > Now, if I make changes to the framework and recopy over the new
    > framework, I get 155005 errors because the .svn file becomes confused
    > with the new folder.
    >
    > Am I just doing this all wrong?  Should I not put the framework bundle
    > into subversion in my project?
    >
    > Thanks for any help or pointers to the correct docs.

    This is better suited for the Xcode list, but no. In my (and many
    others') opinion you shouldn't put your built products into your svn
    repository. You end up with a whole lot of nonsense bloat, and hassle
    as you describe. Instead your Xcode project should simply reference
    the built products (that are still sitting in the build directory) of
    other projects (easiest if you use a shared directory). Also you
    should use a project dependency in your app's project pointing to the
    framework's project so that they'll automatically build together etc.

    There are some docs in Xcode about project dependencies, and you ask
    more about this on the Xcode list before Scott throws down the law
    since this isn't directly related to Cocoa.

    --
    Seth Willits