• 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: Xcode and Confidentiality (was: xcode 2.2 editor problem)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)


  • Subject: Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)
  • From: Dair Grant <email@hidden>
  • Date: Tue, 8 Nov 2005 20:46:00 +0000

Greg Hurrell wrote:

>What stance do other developers in my situation adopt with respect to
>trying out these new Xcode builds? I know that the use of pre-release
>software is always a "use at your own risk" affair, but I'm wondering
>how many decide to actually run that risk on their production
>machines. Thoughts?

I never install them, for exactly this reason - we don't have a
dedicated build machine for preparing releases to clients, so it's
normally the main engineer on a project who prepares the build.

It is a bit frustrating, as you end up reading about bugs which have
been fixed and get pestered by Radar to re-test bugs you've filed (which
won't happen, so it's not consequence-free for Apple). On the plus side,
you never run the risk of shipping anything important with pre-release
tools.


I would really like it if Xcode was, like CW, a "regular application".
I.e., one you could install anywhere, and have multiple versions of it
installed simultaneously. I regularly used to keep 3 releases of CW on
the same machine for current/legacy projects - but Xcode is much more of
an all-or-nothing affair.

This gets worse with multiple developers: upgrading tools just prior to
a release is always risky, so if you have several projects overlapping
it's difficult to find a good time for everyone (even more so if the
project format changes).

At the moment the Mac OS X build environment (i.e., Xcode and the SDK
system) is, IMO, too tightly bound to the OS - if you want multiple
Xcodes you need multiple boot partitions, and switching between them
means a reboot.


-dair
___________________________________________________
mailto:email@hidden     http://www.zonic.co.uk/
 _______________________________________________
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

  • Follow-Ups:
    • Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)
      • From: "Sean McBride" <email@hidden>
  • Prev by Date: Re: xcodebuild can't find gcc?
  • Next by Date: Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)
  • Previous by thread: Default shell used by worksheets
  • Next by thread: Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)
  • Index(es):
    • Date
    • Thread