Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#15 Ignore repository irrelevant files

closed-fixed
nobody
General (4)
5
2011-07-23
2011-05-05
Pit Palme
No

printf "build\n" | svn ps svn:ignore -F - .
printf "xcuserdata\nproject.xcworkspace\n" | svn ps svn:ignore -F - iAlertU.xcodeproj

executed on command line when in working directory would configure SVN to ignore those files being created when building, so commits and patch creation might be easier. At least the files in iAlertU.xcodeproj might result from me using XCode 4 and might be different for 3.2 ...

Discussion

  • Pit Palme
    Pit Palme
    2011-05-05

    • labels: --> General
     
  • Peter Easdown
    Peter Easdown
    2011-07-21

    Hi Pit,

    Finally getting around to applying your patches. Can you please give me a bit more info on this one? I've transitioned to xcode 4 as well now.

    Thanks

    ezsource

     
  • Pit Palme
    Pit Palme
    2011-07-22

    Hi,

    if you check out iAlertU and build it, directories

    ./build
    ./iAlertU.xcodeproj/xcuserdata
    ./iAlertU.xcodeproj/project.xcworkspace

    are created by XCode (4).

    As far as I know, and was able to find out, these directories contain only information relevant to the local working copy, i.e. XCode stores build and workspace relevant stuff in it.
    I don't think it's useful to commit these directories (and their files) to the repository.
    First because it contains build results (./build/) that don't belong into the SCM.
    Second because it contains user and "local XCode installation"-specific settings and files (./iAlertU.xcodeproj/xcuserdata & ./iAlertU.xcodeproj/project.xcworkspace) ... See the files in these directories; They are partially named after my username ...

    But if you do 'svn st' you get these directories and files as "changes" and that makes it harder to either commit (if you've got write permission) or create patch files, because you've got to sort them out manually.

    Setting 'svn:ignore' property tells svn to ignore these directories.
    This makes 'svn diff' ignore these files (and directories) too, and prevents any svn command "warning" you about unversioned files.

    But as you have to set 'svn:ignore' on the directory directly containing the affected directories (or files) you can't set all of them to 'ignore' on top level.
    Only './build/' can be set to ignore on top level, as it's located there.
    The directories within './iAlertU.xcodeproj/' need to be ignored within svn settings of this directory.
    Hence the two commands.

    And as you can't create a patch file for changed properties (whether 'svn:' properties or not) I had to present the two commands, instead of uploading a .patch file.

    If this wasn't the "mor info on this one" you've requested I beg your pardon for misunderstanding ... Maybe the things you requested are too obvious to me for recognizing you'd ask for them :-)

    Regards,

    Pit

     
  • Peter Easdown
    Peter Easdown
    2011-07-23

    • status: open --> closed-fixed
     
  • Peter Easdown
    Peter Easdown
    2011-07-23

    OK, understood. I thought that might be it, but I wanted to be sure before I did it.

    Thanks again,

    ezsource