Re: Packaging a header-only library with frequent breaking changes

2023-01-17 Thread Andrius Merkys
Hello, On 2023-01-17 15:04, David Kalnischkies wrote: I would suggest talking to maintainers of similar packages, they can probably give you more practical advice in this matter. I maintain a couple of similar header-only packages. Developers unwilling to provide stable API are a challenge,

Re: Packaging a header-only library with frequent breaking changes

2023-01-17 Thread David Kalnischkies
Hi, On Sun, Jan 15, 2023 at 01:21:59PM +, Matthew Fennell wrote: > I'm looking into whether it is feasible to package EnTT [1], a header-only C++ > library with breaking API changes every few releases / months. As I use it in a private toy-project I can certify that it is breaking API (and

Packaging a header-only library with frequent breaking changes

2023-01-15 Thread Matthew Fennell
Hi all, I'm looking into whether it is feasible to package EnTT [1], a header-only C++ library with breaking API changes every few releases / months. Would the following approach be sufficient to prevent reverse dependencies from having dependency issues when the library is updated: 1) Create a