On Thu, Feb 6, 2020 at 6:44 AM Thorsten Kukuk <kukuk(a)suse.de> wrote:
On Wed, Feb 05, David C. Rankin wrote:
Is this really warranted? When workarounds are
needed to correct a new change
-- there is a problem. And for 20+ years, every program that needs a specific
port has looked to /etc/services. That means every program (other than those
updated or patched by the opensuse team) will fail to find the services file
in the new location (unless patched by the user)
No application is reading /etc/services directly. They all use the glibc
interface for this.
No need to patch any application.
True for clients that access service definitions. Not at all true for
software installers that add services to the services file. Our
installer is not RPM based as it does lots of things beyond what RPM
allows. It will have to now detect where to add new services. If there
was a program that could be told a service and add it if it does not
exist, then what you say might be true. But most installers like ours
check if a service is defined, and if not, add it to the services
file. So it needs to know the location. Is there a user command that
tells the name of this file?
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org