no releases from last year, is it supported or should i move to or spm?
Never mind releases, our build now takes an indeterminate amount of time because this thing hangs. Every single time.. seriously one of the worst tool breakdowns ever. Do NOT start using this unless the only other alternative is a year on an aleutian island scrounging for rat meat.
Well, the PRs have gotten some code reviews, but no merges in awhile. Not clear why.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Any updates here? Are you in need of new maintainers? I'd be happy to volunteer my time.
@evandcoleman help is always appreciated, especially in triaging new issue
I checked out the code and I am trying to add at least support for binary xcframeworks, based on open PRs from @tmspzz (thanks a lot for that work), cause it seems in the full scope of xcframework support they will not be merged soon. And I could use some xcframeworks for Unity and Kotlin Mutliplatform generated binaries.
I always like to test my code, so I wanted to check it out, and apply some unit tests. It seems Project.swift could use some breakdown, into smaller classes with clear set of responsibilities (DependencyInstaller class could be one). This is what I am struggling most with any change here, and probably something that increases the level of effort for anyone willing to contribute.
Anyway, I got the feeling over the years of using Carthage, and reading through issues here, that changes are not always really welcome. Maybe this is just a feeling, maybe things changed, but if I am going to work on it, refactor, improve a bit in terms of SOLID, commit my personal time, are those changes going to be approved?
@michallaskowski changes are welcome, however since I'm "in charge" of that PR if you want to continue I can give you some pointers on the direction to take. You can contact me on twitter and we'll figure out how to sync.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
Never mind releases, our build now takes an indeterminate amount of time because this thing hangs. Every single time.. seriously one of the worst tool breakdowns ever. Do NOT start using this unless the only other alternative is a year on an aleutian island scrounging for rat meat.