Bug 9893 - Wrong installation path for PIDL Perl modules
Summary: Wrong installation path for PIDL Perl modules
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: PIDL and libndr (show other bugs)
Version: unspecified
Hardware: All All
: P5 minor (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-16 14:13 UTC by Vadim Zhukov
Modified: 2021-03-22 02:34 UTC (History)
0 users

See Also:

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 Vadim Zhukov 2013-05-16 14:13:21 UTC 
On OpenBSD, Perl modules should be installed under ${PREFIX}/libdata/perl5 folder. Unfortunately, pidl/lib/wscript_build (as of Samba4) forcibly installs them under ${DATAROOTDIR}/perl5. So we likely either need either to add another configuration option; or to detect such situation, say, by parsing and interpreting "perl -V" output; or to do both things, defaulting first one to the data gathered via second. What way will be more correct and acceptable for you?

For now, I just patch the pidl/lib/wscript_build itself.
Comment 1 Jelmer Vernooij 2013-05-16 21:12:04 UTC 
I'm not really a fan of adding another configuration option. A patch that parses the "perl -V" output would be great.
Comment 2 Andrew Bartlett 2019-04-01 21:20:25 UTC 
Moving PIDL bugs into Samba as we do not release PIDL separately.
Comment 3 Andrew Bartlett 2021-03-22 02:34:35 UTC 
We no longer install PIDL from waf, we use the MakeMaker based system which should be closer to traditional Perl behaviour (I hope). 

Fixed in master with e24e344d0da58013fd5fa404529fe1d25ef403bf and Samba 4.11 with d42c7ffa6cbd90d0e777e39b12eda5c69e186a2f