Discussion: How to improve install process and documentation #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is a demonstration PR to facilitate the discussion started in #22 . In my opinion it is too difficult to install this library, at least on a mac. A number of recent issues (#8, #28, #30, #36) demonstrate that it is causing frustration.
My suggestion, only partly implemented here, is to use the existing package management systems for both Emacs and SuperCollider to distribute the scel packages.
.sc files are required to be installed in supercollider. If we publish a quark, this can be as easy as executing this on the installation machine:
The emacs side can be handled with the package manager of the user's choosing. Here's what it looks like in my Doom config:
We can publish a melpa package description too, once this is merged to main. Something like:
This is still a draft because there are open questions / todos, but I wanted to open this up for early feedback and discussion
Some discussion now happening on scsynth.org