Project

General

Profile

Actions

Bug #6300

closed

build: RPM has libosmo-mgcp-devel, but debian does not

Added by neels 5 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/11/2023
Due date:
% Done:

100%

Spec Reference:

Description

AFAICT, the situation should be:

  • we only install libosmo-mgcp-client headers from include/mgcp_client/.
  • we do not install any headers from include/mgcp/.

The actual situation is:

  • debian/ does as I expect above, there is only a libosmo-mgcp-client-dev package.
  • include/Makefile.am lists include/mgcp/*.h as installed headers.
  • contrib/osmo-mgw.spec.in installs libosmo-mgcp-client-dev, but it also installs libosmo-mgcp-dev with include/mgcp/*.h headers.

The RPM spec was imported from opensuse in
d6877eb8f979524e0af3c9596f1a3cec069813e0 I6d6119ca5debf4adfec6c155f81027c8a3583537

It seems to me that mnhauke saw our mgcp/*.h that were installed by Makefile.am by accident,
and that's why we now also have it in the RPM spec.

We should remove it from the RPM spec, i.e. drop libosmo-mgcp-dev,
and in the Makefile.am move it to noinst_HEADERS.

Right?

Actions #1

Updated by osmith 4 months ago

Makes sense to me

Actions #2

Updated by neels 4 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)