You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
x/sys/execabs was introduced after we introduced the internal/execabs package in 2021 in order to fix a security issue, so that the same functionality could be used in external packages. In 1.19 we changed the default behavior of os/exec to match internal/execabs, and removed that package.
At this point it seems reasonable to deprecate x/sys/execabs, and point people at os/exec again.
The text was updated successfully, but these errors were encountered:
It probably has enough existing usage that we shouldn't tag-and-delete yet. (Most of the other tag-and-delete packages were unmaintained and virtually unused for many years prior to deletion.)
But I wonder if we should put this on hold until we have a //go:fix tool available, to minimize the amount of work needed for users to resolve the deprecation notices. Given that it is such a thin wrapper around os/exec, the maintenance cost of keeping it around in the meantime doesn't seem particularly high.
x/sys/execabs was introduced after we introduced the internal/execabs package in 2021 in order to fix a security issue, so that the same functionality could be used in external packages. In 1.19 we changed the default behavior of os/exec to match internal/execabs, and removed that package.
At this point it seems reasonable to deprecate x/sys/execabs, and point people at os/exec again.
The text was updated successfully, but these errors were encountered: