On Sat, Oct 13, 2012 at 9:00 PM, bunk3m wrote:
> So where did the Xcode apps and files that used to be in /Developer go in
> this new version (ML)?
>
They're inside the app bundle for /Applications/Xcode.app.
> At one point we had the choice to install skds for 10.6, 10.5 etc. What
> does one
Thank you Brandon & Jeremy.
On the first run, Xcode didn't give me the option to remove. So I
tried Brandon's suggestion:
sudo /Developer/Library/unins
tall-devtools --mode=all
This removed mostly everything. I put the left over from /Develope
On Sat, Oct 13, 2012 at 8:28 PM, bunk3m wrote:
> Then I downloaded Xcode 4.5.x from the App Store. Now Xcode is in the
> /Applications folder. It used to be inside /Developer/Applications/ folder.
>
> I see that the /Developer folder still exists. And there is still another
> Xcode 3.2.6 insta
There should be an uninstall script for xcode 3... check out its readme file
bunk3m wrote:
>Hi.
>
>I'm confused and haven't found the answer to this yet.
>
>I did an in-place upgrade from Snow Leopard to Mountain Lion. (Yes, I
>know a full and fresh install would have been better, but I don't h
Hi.
I'm confused and haven't found the answer to this yet.
I did an in-place upgrade from Snow Leopard to Mountain Lion. (Yes, I
know a full and fresh install would have been better, but I don't have
time to install all the various apps.)
As I use a number of MacPort apps I had already done
On Sat, Oct 13, 2012 at 10:19 AM, Ryan Schmidt wrote:
>
> On Oct 13, 2012, at 10:10, Rodolfo Aramayo wrote:
>
>> Buildbots are great and welcome and can produce binaries that can be
>> reliable used in different machines of the same 'uname -m'
>> architecture
>
> Our binaries are tagged with the a
On Oct 13, 2012, at 10:10, Rodolfo Aramayo wrote:
> Buildbots are great and welcome and can produce binaries that can be
> reliable used in different machines of the same 'uname -m'
> architecture
Our binaries are tagged with the architecture. Currently we only have binaries
for x86_64.
> BUT
Ryan,
Buildbots are great and welcome and can produce binaries that can be
reliable used in different machines of the same 'uname -m'
architecture
BUT MacPorts is more than that
MacPorts does interact with directories outside '/opt/local' like the
'/Users/Applications/MacPorts'
And Macport cannot
On Oct 13, 2012, at 02:34, Rodolfo Aramayo wrote:
> Hi Petra,
>
> Regarding your question
>
> Do not do that
>
> I currently manage >15 computers with MacPorts installed and I can
> tell you that each machine is a universe on its own. Even those who
> are 'identical' at the hardware and softwa
Hi Petra,
Regarding your question
Do not do that
I currently manage >15 computers with MacPorts installed and I can
tell you that each machine is a universe on its own. Even those who
are 'identical' at the hardware and software level they are not really
absolutely equivalent and that depends on
10 matches
Mail list logo
