On 01/02/2023 11:51, Neal Gompa wrote:
On Wed, Feb 1, 2023 at 12:46 PM Benson Muite wrote:
For Catch, there was an upgrade from 1 to 2. Similarly for FFTW, the
main package uses the name FFTW, but it was FFTW3 before hand. Maybe one
could use Catch3 or Catch2v3? Then change names later once mo
On Wed, Feb 1, 2023 at 12:46 PM Benson Muite wrote:
>
> The review had gone through, and had created the package, then retired
> it, but as the APIs are different, and this also applies to another
> package I have under review, mbedTLS, wanted to know if there are
> general guidelines on this.
>
>
an to do it again so I don't know what more you want.
>
> Tom
>
> On 01/02/2023 10:13, Benson Muite wrote:
>> Packages with breaking APIs between major version changes often keep
>> maintaining the older version for some time after the new version is
>> rel
There is already precedent for doing it with catch and I've said
that I plan to do it again so I don't know what more you want.
Tom
On 01/02/2023 10:13, Benson Muite wrote:
Packages with breaking APIs between major version changes often keep
maintaining the older version for some
Packages with breaking APIs between major version changes often keep
maintaining the older version for some time after the new version is
released. An example is FFTW which has both FFTW (version 3) and FFTW2
(version 2) within Fedora:
https://packages.fedoraproject.org/search?query=fftw
Is it
