Custom sections are identified by unstructured string names, which presents the possibility of conflicts between different tools. This repo helps the situation by acting as a pseudo-registry of some "publicly well-known" custom section names, but doesn't help with less-common or private tooling.
I'd like to suggest that this repo publish a recommendation for formatting custom section names to help avoid conflicts. One obvious source of inspiration might be vendor mime types (e.g. vnd.acme.whatever) but I'm less concerned about the exact format than the general idea.
Custom sections are identified by unstructured string names, which presents the possibility of conflicts between different tools. This repo helps the situation by acting as a pseudo-registry of some "publicly well-known" custom section names, but doesn't help with less-common or private tooling.
I'd like to suggest that this repo publish a recommendation for formatting custom section names to help avoid conflicts. One obvious source of inspiration might be vendor mime types (e.g.
vnd.acme.whatever) but I'm less concerned about the exact format than the general idea.