• 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
Which XCode files to version control? (Was: .mode1 files and version control)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Which XCode files to version control? (Was: .mode1 files and version control)


  • Subject: Which XCode files to version control? (Was: .mode1 files and version control)
  • From: Heath Raftery <email@hidden>
  • Date: Wed, 11 Aug 2004 15:45:08 +1000

I've wondered this for a while now, but Christian's post motivated me to put it in an email.

On 11/08/2004, at 2:47 PM, Christian Pekeler wrote:
I typically have .pbxuser files under version control, mainly to
archive launch parameters. I've noticed that as of Xcode 1.5 there are
now also .mode1 files for each user in the .pbproj directory. What's
their purpose? Would it make sense to have them under version control,
too?

I don't have any answers here, but was hoping to extend the query somewhat. Using Borland RAD tools, version control is very difficult because all the user settings (history lists, recent items, window sizes) are in the same file as the project structure. You couldn't update to someone else's project file because it would override all your custom settings, usually breaking lots of things. In particular, if a file was added to the project, you could update and get the new file fine, but would have to add it and categorise it in the project manually, because you couldn't update to the project settings file as easily.


I always thought this was poor design - user settings should be seperate to project metadata. The latter defines the project, the former defines customisations which the project itself need not no about. That is, if you were to remove all the user settings (revert them to default say) all the information you needed to build the project would be in the project settings.

Unfortunately, I'm seeing similar design with XCode! Inside the project.xcode package are/were two files (as Christian mentions) but after looking inside I can't be sure that there is a seperation between say, saved window sizes, and project source groups.

Is it safe to commit one and not the other? Is there any official word here? And was or is this seperation of project and user settings a consideration in XCode's development?

Regards,
Heath
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: Which XCode files to version control? (Was: .mode1 files and version control)
      • From: Scott Tooker <email@hidden>
    • Re: Which XCode files to version control? (Was: .mode1 files and version control)
      • From: Scott Tooker <email@hidden>
References: 
 >.mode1 files and version control (From: Christian Pekeler <email@hidden>)

  • Prev by Date: How do you localise the file name of an application?
  • Next by Date: Re: Xcode 1.5 and NFS problems?
  • Previous by thread: .mode1 files and version control
  • Next by thread: Re: Which XCode files to version control? (Was: .mode1 files and version control)
  • Index(es):
    • Date
    • Thread