Skip to content
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

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

relikd
Copy link

@relikd relikd commented Aug 5, 2019

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.

@relikd relikd changed the title Add support for additional framework extensions (#2834) Add support for additional framework extensions Aug 5, 2019
@tmspzz
Copy link
Member

tmspzz commented Aug 5, 2019

I'm surprised how little work this took. Well done 👍

Copy link
Member

@tmspzz tmspzz left a 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

Source/CarthageKit/ProductExtension.swift Outdated Show resolved Hide resolved
Copy link
Author

@relikd relikd left a 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.

Source/CarthageKit/ProductExtension.swift Outdated Show resolved Hide resolved
Source/CarthageKit/ProductExtension.swift Outdated Show resolved Hide resolved
@mdiep
Copy link
Member

mdiep commented Aug 6, 2019

Yup, that's what I was thinking

Source/carthage/Archive.swift Outdated Show resolved Hide resolved
Oleg Geier and others added 2 commits August 8, 2019 13:34
Co-Authored-By: Robert Böhnke <212465+robb@users.noreply.github.com>
@jdhealy jdhealy self-requested a review August 8, 2019 11:43
@relikd
Copy link
Author

relikd commented Aug 8, 2019

remoteVersion__should_time_out failed. I heared that this happens quite frequently?

@tmspzz
Copy link
Member

tmspzz commented Aug 8, 2019

@relikd yeah, don't worry about that one.

@relikd
Copy link
Author

relikd commented Aug 24, 2019

@jdhealy you self-requested a review a while ago, did you find time?

@stale

This comment has been minimized.

@stale stale bot added the stale label Sep 23, 2019
@jdhealy jdhealy removed the stale label Sep 24, 2019
@relikd
Copy link
Author

relikd commented Oct 30, 2019

Sad to see that after two months nothing really changed. Can you re-run Travis so that the checks succeed?

@relikd
Copy link
Author

relikd commented Mar 21, 2020

Hey ho, I merged the upstream changes.
However I am not sure why Travis shows All checks have failed. Each log returned with error code 0 and 0 failed test.
@tmspzz @jdhealy Is there a timeout limit? Travis was down for maintanance for a few hours. Therefore the test run show 7 hours running.

@relikd
Copy link
Author

relikd commented May 13, 2020

Is it ok to bump the topic every once in a while?
I've merged upstream changes and all checks are passing. PR is ready …

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants