XcodesOrg / XcodesOrg/XcodesApp

Run a Custom Install

Open
#396 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Swift
Stars
8.6k
Forks
387
Avg merge
6d 7h
Merged PRs (30d)
3

Description

Custom-Run Install Profiles

I'd like to make sure that all of the features I want to be installed with a particular Xcode version are properly recognized by the Xcodes app as being part of said install, even when all of the installation files are downloaded manually from Apple. For example, in browsing the More Downloads section of the Apple Developer website, I found exactly what I was looking for, in terms of packaged components of Xcode, as well as the Xcode app itself, that I wanted to install, but I am worried that, given there is no way to give these files to the Xcodes app to be installed explicitly side-by-side to my Mac App Store Xcode install, that I am either going to accidentally replace my Mac App Store version with this downloaded one, or that Xcodes will not properly recognize all of the components I want associated with this separate Xcode install, such as the Additional Tools package and others.

Details

It would be nice to simply have a feature where you can fill out a form in the app that asks you for images for various components, and then associates them all to one particular install "profile", where you can have multiple of the same version, if, for example, you want to have a different setup for a different workload, and maybe want a different version of some additional package available while the profile is active, but can also use this to make sure you have all the components you want available, such as the latest version of the Xcode beta and its additional packages, all associated together as an install "profile".

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the existing Xcodes app install and version-switching flow, then determine how manually downloaded Xcode components and multiple install profiles should be represented. Done means users can create separate profiles, associate component files with each profile, and keep those installs distinct.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
desktop, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.