Exactly the same question has been asked 8 years ago at OSX .pkg deletes other dev versions
The answer was
pkgbuild does not support not overwriting the previous version at this time
Is there any news or does the same restriction still apply today?
According to this comment: Mac installer overwrites ALL copies of file, setting BundleIsRelocatable to FALSE fixes this.
Related
I seem to be having this really weird issue where Github Desktop doesn't open any windows on the mac.
Upon setup I had a window to sign in and choose my repo but after that set up no window shows up
Anyone else had an issue like this?
Is there a way I can provide log/error files?
This sounds like the same problem I had, for which I contacted GitHub Support. They suggested deleting GitHub Desktop and downloading a fresh copy (e.g., 222 in my case), then unarchiving it with the Mac Archive Utility instead of a third-party archiver (I had used WinZip). This resolved the windowing problem I had.
I had a similar problem and I resolved it by simply unzipping a fresh copy of GitHub Desktop.
I used "TheUnarchiver app" (https://itunes.apple.com/it/app/the-unarchiver/id425424353?mt=12) for this, (but any unpacking software should to the trick).
I have imported a new iPhone Developer Certificate in my keychain and deleted the old one since Xcode does not want to choose between two certificates when signing code (even when one is no more valid).
What's weird is that this old certificate sometimes shows up again whereas I already deleted it. So, I have to delete it several times a week.
Did someone face this issue ? Any idea to fix that ?
Many thanks,
Franz
I answered a similar question here. I'm assuming you are using XCode 4, so your best bet is to follow my instructions for clearing out all your old stuff, and letting XCode do the legwork for you.
Switching to Xcode 4.2 (for Snow Leopard) solved the issue.
I recently installed Mac OS X on my system. This is probably a very basic question but when I run make it says make not found and there is no make under usr/bin. How to correct this?
The easiest way to get make, gcc and so on is to install Xcode (this can be found on the 'Applications' DVD that came with your computer, or you can download it from the Apple website, or you can download it from the App Store).
However, the Apple versions of those packages are old - you can use MacPorts to get newer, improved versions of those.
Can I install two versions of Xcode on my Mac? I'm planning to install 10.5 and 10.6. If this is possible please let me know...
Kevin
I'm sorry, what? The version of xcode on snowy builds 10.5 and 10.6 apps. If you partition your hard drive and have 10.5 and .6 on each separate partition then you need xcode on each one to work
If you have OS X 10.6, you should be able to target 10.5 (as well as 10.6, of course) from within that version. You should not have two separate installs of Xcode.
Maybe do some Googling to find out more details on how to do it. Here's something to get you started.
As others have already pointed out, installing two version of Xcode is probably not necessary. However, to answer the question directly, it is possible to do so. At install time, you will need to specify a directory different than the default. For instance, instead of /Developer/... put the second install in /DeveloperXcode3.1/... or something like that.
That said, the only time I've found a need to do that is with beta versions.
I've just unwrapped my new MacBook Pro (yay!) and am now setting it up properly for development. Since I want to avoid clutter, I'm wondering if I really need to install the Xcode tools at all (I never use the IDE or Mac specific tools), since I'll install a newer version of GCC anyway, using MacPorts.
So, is there any benefit in installing Xcode? Is it necessary? What kind of set-up does it do behind the scenes? Basically: can I skip this or will it come back to haunt me because some Unix development tools just assume that OS X is always set up in this way?
In order to perform an easy and successful install of MacPorts, already having tools from the xCode installer is necessary. You only need the install option that places a copy of the unix/header files outside of xcode; everything else can remain uninstalled.
A friend of mine recently released this:
https://github.com/kennethreitz/osx-gcc-installer
Have fun :)
I tried this trick and I was constantly chasing missing header files and such. Just install XCode.
We primarily use the Xcode IDE for building Cocoa/Carbon applications. Xcode typically has different project templates (and project settings fixed accordingly). As long as you are not going to generate a Universal Binary or a framework I think you should be ok. As far as I am concerned, when I am too pissed with Xcode, I go back to the command line, set up the paths myself and start using GDB.
First of all, congratulations on the new MBP. I recently bought a 15" unibody myself. =)
You can safely skip Xcode installation, and you can install almost everything Xcode installs through MacPorts, except Xcode itself, of course.
However, I believe you'll find yourself installing Xcode one day anyway, and installing Xcode is much easier than installing all the tools (especially GCC) through MacPorts.
You can strip down the Xcode install quite a lot - when you install Xcode there is a "Customise" button where you can remove a lot of stuff (gigabytes worth).
You can also go in and delete stuff from /Developer/, for example the 10.3 SDK is about 150MB (I think), and if you're not writing software for that it's quite safe to delete. Obviously be careful when deleting, but if you break things, you can always reinstall the Developer Tools!
Apple now provides the command line tools as a separate download from Xcode. They work with Lion and Mountain Lion. You can download them from the Apple Developer Center.
(This is noted on the osx-gcc-installer GitHub page.)