Will a forked repo be accepted?

[playgithub]

The lib (cppjieba) is not popular, and it depneds on an even less popular lib (limonp) and gtest.
In the original lib, the depnedencies are simply copied there, including limonp and gtest.

It needs many refactors, so I want to fork it and refactor it, will vcpkg accept a forked repo like this?

[playgithub]

OK, it will, better be marked as unofficial.

[ghost]

@playgithub did you get any answer regarding this offline ? i am also thinking forking other opensource projects.

[dg0yt]

There is no such official interface for Poppler. That's the reason why vcpkg provides a private/unofficial config. The unofficial prefix is a warning that these identifiers will be dropped when Poppler starts to export official config.

[dg0yt]

Read more:
https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md#add-cmake-exports-in-an-unofficial--namespace

[playgithub]

There is no such official interface for Poppler. That's the reason why vcpkg provides a private/unofficial config. The unofficial prefix is a warning that these identifiers will be dropped when Poppler starts to export official config.

OK, it's in extra cmake modules by KDE (https://api.kde.org/ecm)

[dg0yt]

OK, it's in extra cmake modules by KDE (https://api.kde.org/ecm)

This is a third-party Find module. And it shares the disadvantages of find modules for non-trivial packages:

• useless for static linkage because unable to know the transitive usage requirements (which depend on configuration), unless it can get them from pkg-config
• unaware of multi-config configuration (release+debug).

But let's stop here. The CMake package topic is unrelated to the forked repo topic.

[Neumann-A]

There is already a port for ecm, if i remeber correctly. It is just called differently