Re: Back to the topic of changed binary named (Was: Lottery NEW queue (Re: Are libraries with bumped SONAME subject of inspection of ftpmaster or not))
On Mon, Jan 24, 2022 at 08:15:30AM +0100, Andreas Tille wrote:
> Hi Paul and others,
>
> its surely an interesting topic how to avoid binary name changes and its
> also interesting to discuss ABI changes and workarounds.
>
> However, my point was that I want to know what policy ftpmaster applies
> to new binary names and to focus on this topic. I really want to know
> that policy of ftpmaster and I really would like to see that documented
> and I'm afraid that thread is drifting away from the original topic
> that I will not get any answer on this.
As far as I know, ftpmaster requires a long, laborious review every
single time there is a new binary package released. As a result, it
strongly disincentivizes maintainers from packaging up new releases
because it's a pain in the posterior. A while back, people asked me I
could update f2fs-tools, and it was shortly before the release freeze,
and even though there was apparently security fixes involved that
would be fixed in the latest version of f2fs-tools, I knew there would
be no point, since there was no way the package would squirt out the
review pipeline before the release freeze.
Even if it isn't formal policy, the long delay has happened enough
times that I just assume it will be there, and it influences my
behavior accordingly.
- Ted
Reply to: