• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Adding existing svn files to new project
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Adding existing svn files to new project


  • Subject: Re: Adding existing svn files to new project
  • From: Quincey Morris <email@hidden>
  • Date: Tue, 25 Aug 2009 12:02:18 -0700

On Aug 25, 2009, at 11:07, Brian Zwahr wrote:

What if you have multiple individual components developed, each in their own version control repository (as they should be), then you want to use them in a new project, also under version control. It seems like you would have to check them out, add them to the new project, commit them to version control in the new project, and then you have two different versions of it in version control.

There is an Xcode solution to this, though it's less than ideal.

There's nothing to prevent you from creating an Xcode project that simply acts as a container for version-controlled files, with its own repository that includes the container project.

Then you can add this container project to your dependent project that's connected to a different repository, and Xcode will know which repository each source file comes from. It works just fine, except that:

-- Adding the container project to the dependent project doesn't add its files to the dependent project. You have to do that separately. (But you can drag selected groups and files from one project window to the other, so it's not so hard.)

-- You have to update each repository separately from its own Xcode project window. (That's a minor nuisance, except that Xcode -- already flaky enough in showing the SCM status for file within a project -- is much flakier showing the status for files in a referenced project that are edited in the referencing project's context. You end up refreshing the SCM status a lot.)

-- You have to be careful when adding files to add them to the right project, and when renaming or deleting files to not do it from the wrong project. It's really easy to get a project into a state where every SCM operation produces unhelpful error messages and there's no obvious solution.

-- Refactor isn't very reliable across multi-project SCM files. Sometimes it works just fine, sometimes it produces spurious error messages, and sometimes it craps out after having changed half the files.


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Adding existing svn files to new project (From: Brian Zwahr <email@hidden>)
 >Re: Adding existing svn files to new project (From: Joar Wingfors <email@hidden>)
 >Re: Adding existing svn files to new project (From: Brian Zwahr <email@hidden>)
 >Re: Adding existing svn files to new project (From: Brian Zwahr <email@hidden>)
 >Re: Adding existing svn files to new project (From: Joar Wingfors <email@hidden>)
 >Re: Adding existing svn files to new project (From: Brian Zwahr <email@hidden>)
 >Re: Adding existing svn files to new project (From: Jeremy Pereira <email@hidden>)
 >Re: Adding existing svn files to new project (From: Brian Zwahr <email@hidden>)

  • Prev by Date: Re: GDB: Getting information about a window
  • Next by Date: Re: GDB: Getting information about a window
  • Previous by thread: Re: Adding existing svn files to new project
  • Next by thread: Re: Adding existing svn files to new project
  • Index(es):
    • Date
    • Thread