New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for additional framework extensions #2843
base: master
Are you sure you want to change the base?
Conversation
I'm surprised how little work this took. Well done 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me. Let's hear from @Carthage/carthage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. Something like that?
I'd like to keep the ProductExtension.supportedExtensions
as it is very similar to Platform.supportedPlatforms
to improve readability.
Yup, that's what I was thinking |
Co-Authored-By: Robert Böhnke <212465+robb@users.noreply.github.com>
|
@relikd yeah, don't worry about that one. |
@jdhealy you self-requested a review a while ago, did you find time? |
This comment has been minimized.
This comment has been minimized.
Sad to see that after two months nothing really changed. Can you re-run Travis so that the checks succeed? |
Is it ok to bump the topic every once in a while? |
Adds support for the following bundle extensions:
.framework
,.action
,.bundle
,.kext
,.mdimporter
,.metallib
,.plugin
,.prefPane
,.qlgenerator
,.saver
,.xpc
Including (un-)archiving as well as support for binary releases.
This list can be extended in
ProductExtension.swift
.Should streamline plugin creation (e.g., QuickLook plugins) and integration in other projects.