> Shouldn't it be autoconf2.71, assuming that it is for autoconf 2.71?
Yes, but in the case of autoconf2.71, I am wondering how to deal with an
update since this package should be the latest version.
Creating package autoconf2.72 in the future doesn't make sense to me.
My thought was to use
* Dominik Mierzejewski:
> On Thursday, 23 September 2021 at 09:52, Filip Janus wrote:
>> Hi all,
>> I am wondering about the right name for Autoconf compact package. I need to
>> add the latest release of autoconf into EPEL so I need a package with a
>> different name. Currently, there are in
On 23. 09. 21 12:51, Dominik 'Rathann' Mierzejewski wrote:
On Thursday, 23 September 2021 at 09:52, Filip Janus wrote:
Hi all,
I am wondering about the right name for Autoconf compact package. I need to
add the latest release of autoconf into EPEL so I need a package with a
different name.
On Thursday, 23 September 2021 at 09:52, Filip Janus wrote:
> Hi all,
> I am wondering about the right name for Autoconf compact package. I need to
> add the latest release of autoconf into EPEL so I need a package with a
> different name. Currently, there are in fedora autoconf, autoconf213, and
Hi all,
I am wondering about the right name for Autoconf compact package. I need to
add the latest release of autoconf into EPEL so I need a package with a
different name. Currently, there are in fedora autoconf, autoconf213, and
autoconf268. The latest version is 2.71 so I have few options in my
