New comment by gt7-void on void-packages repository

https://github.com/void-linux/void-packages/issues/29965#issuecomment-813114105

Comment:
> This is a better lint step (looking for duplicates) than failing on an unsorted list.

Is it easy to decide when a duplicate soname is ok or not?

> If someone forgets to sort it then we have 10 PRs all trying to reorder it,

Could we have a lint step checking that the file is sorted?

> affecting more lines than just adding a new soname in a random position instead of the end to avoid merge conflicts for newly added libraries.

Is there a policy about that? I understood sonames had to be placed at (near) the end of the file.

I don't care so much about having the file sorted. The fundamental itch I have is constantly having to amend patches.

The real pain for me was the experience of working with the branch in #29997, which has 7 commits for different packages which add sonames, and any rebase/editing of previous patches would cause a lot of pain. Of course, all this pain would mostly go away if I were to place each soname in a different random place in the file...