Bug 2367 - libpcap recipe does package pcap-config in libpcap instead of libpcap-dev
Summary: libpcap recipe does package pcap-config in libpcap instead of libpcap-dev
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: connectivity (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.3 M2
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard: (M1)(merged)
Depends on:
Blocks:
 
Reported: 2012-04-24 06:53 UTC by Adrien Bustany
Modified: 2012-07-31 15:47 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adrien Bustany 2012-04-24 06:53:21 UTC 
Using meta/recipes-connectivity/libpcap/libpcap_1.1.1.bb, the pcap-config utility is packaged in libpcap and not libpcap-dev (using RPM packaging, is that's relevant).
Comment 1 Saul Wold 2012-05-23 01:23:08 UTC 
This change is much greater than simply moving some files around for packaging, it uncovered a larger issue.

I am going to move this to 1.3 only as it's been this way for a while and does
not harm anything to remain this way.
Comment 2 Saul Wold 2012-06-21 16:33:36 UTC 
This was fixed by reordering the PACKAGES list to place ${PN} at the end and correctly mapping the -config files into ${PN}-dev.

This was a large change set starting at

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f68cbf56d8f2a45ce44a59d0411cdda8ec7e2c36
Comment 3 Laurentiu Serban 2012-07-31 15:47:11 UTC 
Verified with commit fb53d69d9c726e6a663ea276cc440676e20f8326