Skip to content
This repository has been archived by the owner on Dec 15, 2020. It is now read-only.

Vcpkg has replaced coapp #113

Merged
merged 1 commit into from
Jan 25, 2019
Merged

Vcpkg has replaced coapp #113

merged 1 commit into from
Jan 25, 2019

Conversation

Thieum
Copy link
Contributor

@Thieum Thieum commented Jan 24, 2019

Vcpkg has replaced coapp as the de-facto source package manager in microsoft development environment.

Vcpkg has replaced coapp as the de-facto source package manager in microsoft development environment.
@gep13
Copy link
Member

gep13 commented Jan 25, 2019

@Thieum thank you for creating this PR.

Full disclosure, I know next to nothing about C++ Package Management. Do you have a reference for where your statement can be verified? Perhaps we should mention both, as they both still seem to be active?

@Thieum
Copy link
Contributor Author

Thieum commented Jan 25, 2019

@gep13 I understand, there are two references that are of interest:

Acquiring native libraries on Windows is a critical part of the application development process; in our surveys, you told us that 80% of your C++ projects depend on two or more libraries. Despite this, we’ve heard that the current process for acquiring native libraries falls below C++ developers’ expectations when compared to other platforms such as Mac (Homebrew) and Linux (apt-get, yum, etc.)

Another reference is the discussion that took place in the vcpkg repo, considering making a clear statement of the advantages of vcpkg over coapp - it didn't lead to an official statement, but the arguments are of interest still: microsoft/vcpkg#714

CoApp unfortunately suffers from the limits of the platform it's built upon: NuGet. Each of our points about why NuGet isn't currently optimal for C++ applies to CoApp as well.

As for any inquiries about CoApp, I would point you to the CoApp project on GitHub. It seems like there is a response from @virmitio in the issue you linked:

We do apologize for out lack of attentiveness in recent history. Both Garrett and myself have been moved to other projects and have little to no time available for ongoing maintenance of CoApp.
If there are individuals interested in taking responsibility for said tasks, please reach out to me and we will try to make arrangements for such

.

@gep13
Copy link
Member

gep13 commented Jan 25, 2019

@Thieum thank you for providing those links. Based on what I am reading there, I think you are correct in the making this change.

@ferventcoder could you have a final look at this, and if you are happy, I will get it merged in and published.

@virmitio
Copy link

@gep13 In case there's any doubt, this seems perfectly reasonable to me.

If I eventually find the time or a person to take up maintaining CoApp, a future pull request can be made to list both.

@gep13
Copy link
Member

gep13 commented Jan 25, 2019

@virmitio thank you for the confirmation, I appreciate it!

@gep13 gep13 merged commit 9450890 into chocolatey:master Jan 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants