Re: Setting the deployment location
Re: Setting the deployment location
- Subject: Re: Setting the deployment location
- From: Denis Stanton <email@hidden>
- Date: Mon, 2 Feb 2004 09:41:37 +1300
I very much agree with Marc's statement below. The default setting to
install in a secret location had me doing annoying workarounds for a
year before I found that changing DSTROOT to / would give me a sensible
location
One of the great features of Apple's iApps is that someone has thought
out all of the default values so that it just works first time without
having to fiddle around around to create a basic configuration before
you can use it. Building to /tmp is the opposite. Fresh out of the
box the build process appears not to work.
When I compile for deployment I want to see a standard deployment,
which means the WebObjects application should go into the WebObjects
application directory. It is then very easy for a simple person like
me to understand that I can deploy onto the production server by coping
to the matching location.
maybe at some future date I will want my app "turned into a package for
distribution", but that's an advanced requirement that I will
investigate when I need it. I believe the first priority should be to
make the environment work for the beginner.
Denis
On Monday, February 2, 2004, at 07:37 AM, Marc Poirier wrote:
On Mon, 26 Jan 2004 Scott Tooker wrote:
The idea is that by default, when "installing" a build that the
products go into a separate location where you can verify the contents
before dittoing or copying the result into place (since a bad
framework
could seriously hose your system). Another benefit of installing into
a
separate location is this gives you a sparse root that can be turned
into a package for distribution.
By default this separate location is set to be /tmp (the build setting
that controls this is $DSTROOT). Currently there is no UI for
$DSTROOT.
Although we don't recommend it, you can set DSTROOT to "/" to have
things install in place.
I've said this before, but I'll say it again: I strongly disagree.
/tmp is a terrible default for $DSTROOT, and it should not be "not
recommended" to change $DSTROOT to /, which is a way saner value for
the
VAST MAJORITY of development out there. I know that in-house at Apple,
you are doing a lot of system framework and extension development, but
the
rest of the world is not! So maybe /tmp makes good sense as a default
within Apple HQ, but so far as Xcode for the rest of the world goes,
it's
a crummy idea. This is a perenial source of confusion and WTFing.
Marc
_______________________________________________
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.
Denis Stanton
email@hidden
Home: +64 9 533 0391
mobile: +64 21 1433622
_______________________________________________
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.