[ISSUE] glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[ISSUE] glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

New issue by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/20728

Description:
Both packages provide `/usr/bin/rpcgen`, some packages use `rpcsvc-proto` in `hostmakedepends` to be able to build on musl.

I think it should be removed from glibc, put into a sub package or use alternatives.

Re: glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[svenper]

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

New comment by svenper on void-packages repository

https://github.com/void-linux/void-packages/issues/20728#issuecomment-613701408

Comment:
I take it from [the readme](https://raw.githubusercontent.com/thkukuk/rpcsvc-proto/master/README) that it should be possible to replace this package with glibc:

> This package contains rpcsvc proto.x files from glibc, which are
missing in libtirpc. Additional it contains rpcgen, which is needed
to create header files and sources from protocol files.
This package is only needed, if glibc is installed without the
deprecated sunrpc functionality and libtirpc should replace it.

Re: glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[svenper]

[-- Attachment #1: Type: text/plain, Size: 645 bytes --]

New comment by svenper on void-packages repository

https://github.com/void-linux/void-packages/issues/20728#issuecomment-613701408

Comment:
I take it from [the readme](https://raw.githubusercontent.com/thkukuk/rpcsvc-proto/master/README) that it should be possible to provide/replace/conflict this package with glibc:

> This package contains rpcsvc proto.x files from glibc, which are
missing in libtirpc. Additional it contains rpcgen, which is needed
to create header files and sources from protocol files.
This package is only needed, if glibc is installed without the
deprecated sunrpc functionality and libtirpc should replace it.

Re: glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[svenper]

[-- Attachment #1: Type: text/plain, Size: 816 bytes --]

New comment by svenper on void-packages repository

https://github.com/void-linux/void-packages/issues/20728#issuecomment-613701408

Comment:
I take it from [the readme](https://raw.githubusercontent.com/thkukuk/rpcsvc-proto/master/README) that it should be possible to provide/replace/conflict this package with glibc:

> This package contains rpcsvc proto.x files from glibc, which are
missing in libtirpc. Additional it contains rpcgen, which is needed
to create header files and sources from protocol files.
This package is only needed, if glibc is installed without the
deprecated sunrpc functionality and libtirpc should replace it.

in glibc (version mismatch though):
```
provides="rpcsvc-proto-${version}_${revision}"
replaces="rpcsvc-proto>=0"
```

in rpcsvc-proto:
```
archs="*-musl"
```

Re: glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/20728#issuecomment-773757288

Comment:
Is this still an issue? Maybe the obsolete RPC removal from glibc took `rpcgen` with it.

Re: glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[ahesford]

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/20728#issuecomment-773758924

Comment:
Our current glibc package does not seem to include rpcgen, so I think this issue resolved itself.

Re: [ISSUE] [CLOSED] glibc and rpcsvc-proto /usr/bin/rpcgen conflict

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

Closed issue by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/20728

Description:
Both packages provide `/usr/bin/rpcgen`, some packages use `rpcsvc-proto` in `hostmakedepends` to be able to build on musl.

I think it should be removed from glibc, put into a sub package or use alternatives.