Re: Request Clarification in package naming convention perl-ldap and perl-LDAP

[email protected] (Joshua Miller) Thu, 21 Mar 2019 20:48:52 -0400
Newsgroups perl.ldap
Message-ID <CAL3qUHfQ7fvYMd4EUWGYwVBJ_8r9BDOs-nSa+4xepX8YUpcrJQ@mail.gmail.com>
--000000000000b039130584a438af
Content-Type: text/plain; charset="UTF-8"

On Thu, Mar 21, 2019 at 8:16 PM Nomalatha Aerampu <
[email protected]> wrote:

> Hi Team,
>
>
> Our application is packaged as RPM and qualified to run in both RHEL and
> SUSE platforms. It has a dependency for perl LDAP module and hence in our
> application RPM spec file we specify perl-LDAP in "Requires" section since
> the earlier SUSE and RHEL releases we had it as follows,
>
> perl-LDAP-0.40-2.el6.noarch
>
>
> In the recent days, while we are qualifying our application for SUSE15
> platform, we see that perl LDAP module is available in the following naming
> convention due to which our "Requires" section is failing,
>
> perl-ldap-0.65-bp150.2.4.x86_64
>
> Even in the following link we see 2 naming (upper case and lower case LDAP)
> https://rpmfind.net/linux/rpm2html/search.php?query=perl(Net%3A%3ALDAP)
> RPM resource perl(Net::LDAP)
> <https://rpmfind.net/linux/rpm2html/search.php?query=perl(Net%3A%3ALDAP)>
> rpmfind.net
> The search service can find package by either name (apache),
> provides(webserver), absolute file names (/usr/bin/apache), binaries
> (gprof) or shared libraries (libXm ...
>
>
That rpmfind search is a major hint. When setting up rpm spec file Requires
or BuildRequires stanzas for perl modules which require something, you
should use that same syntax, rather than a package name. Ex:

    Requires: perl(Net::LDAP)

You can specify a version using that syntax as well:

    Requires: perl(Net::LDAP) >= 0.40

I think this also allows the required module to be installed via rpm or via
a manual install, and the system will go figure it out, but I'm not certain
of that.

Fedora RPM guidelines also mention use of perl(Foo) for requires and
provides:
https://fedoraproject.org/wiki/Packaging:Perl#Perl_Requires_and_Provides

HTH,
--
Josh I.

--000000000000b039130584a438af
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr">On Thu, Mar 21, 2019 at 8:16 PM Nomalatha Aeramp=
u &lt;<a href=3D"mailto:[email protected]">anomalatha@pulsesecure.=
net</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">




<div dir=3D"ltr">
<div id=3D"gmail-m_8863870652701455273divtagdefaultwrapper" style=3D"font-s=
ize:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir=3D"=
ltr">
<p style=3D"margin-top:0px;margin-bottom:0px">Hi Team,</p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">Our application is packaged a=
s RPM and qualified to run in both RHEL and SUSE platforms.=C2=A0<span styl=
e=3D"font-size:12pt">It has a dependency for perl LDAP module and hence in =
our application RPM spec file we specify perl-LDAP
 in &quot;Requires&quot; section since the earlier SUSE and RHEL releases w=
e had it as follows,</span></p>
<p style=3D"margin-top:0px;margin-bottom:0px"><span style=3D"font-size:12pt=
"><span style=3D"font-family:Calibri,Helvetica,sans-serif,EmojiFont,&quot;A=
pple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;,NotoColorEmoji,&quot;Sego=
e UI Symbol&quot;,&quot;Android Emoji&quot;,EmojiSymbols;font-size:16px">pe=
rl-LDAP-0.40-2.el6.noarch</span><br>
</span></p>
<p style=3D"margin-top:0px;margin-bottom:0px"><br>
</p>
<p style=3D"margin-top:0px;margin-bottom:0px">In the recent days, while we =
are qualifying our application for SUSE15 platform, we see that perl LDAP m=
odule is available in the following naming convention due to which our &quo=
t;Requires&quot; section is failing,</p>
<p style=3D"margin-top:0px;margin-bottom:0px"></p>
<div>perl-ldap-0.65-bp150.2.4.x86_64</div>
<div><br>
</div>
<div>Even in the following link we see 2 naming (upper case and lower case =
LDAP)</div>
<div><a href=3D"https://rpmfind.net/linux/rpm2html/search.php?query=3Dperl(=
Net%3A%3ALDAP)" class=3D"gmail-m_8863870652701455273OWAAutoLink" id=3D"gmai=
l-m_8863870652701455273LPlnk666010" target=3D"_blank">https://rpmfind.net/l=
inux/rpm2html/search.php?query=3Dperl(Net%3A%3ALDAP)</a>
<div id=3D"gmail-m_8863870652701455273LPBorder_GT_15530072178710.6929415623=
676389" style=3D"margin-bottom:20px;overflow:auto;width:100%;text-indent:0p=
x">
<table id=3D"gmail-m_8863870652701455273LPContainer_15530072178580.90851443=
78125947" cellspacing=3D"0" style=3D"width:90%;background-color:rgb(255,255=
,255);overflow:auto;padding-top:20px;padding-bottom:20px;margin-top:20px;bo=
rder-top:1px dotted rgb(200,200,200);border-bottom:1px dotted rgb(200,200,2=
00)">
<tbody>
<tr valign=3D"top" style=3D"border-spacing:0px">
<td id=3D"gmail-m_8863870652701455273TextCell_15530072178620.09295312553898=
838" colspan=3D"2" style=3D"vertical-align:top;padding:0px;display:table-ce=
ll">
<div id=3D"gmail-m_8863870652701455273LPRemovePreviewContainer_155300721786=
30.2766827016811426"></div>
<div id=3D"gmail-m_8863870652701455273LPTitle_15530072178630.82591885441826=
38" style=3D"color:rgb(92,185,71);font-weight:400;font-size:21px;font-famil=
y:wf_segoe-ui_light,&quot;Segoe UI Light&quot;,&quot;Segoe WP Light&quot;,&=
quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,Arial,sans-serif;line-heigh=
t:21px">
<a id=3D"gmail-m_8863870652701455273LPUrlAnchor_15530072178650.830999166253=
2645" href=3D"https://rpmfind.net/linux/rpm2html/search.php?query=3Dperl(Ne=
t%3A%3ALDAP)" style=3D"text-decoration:none" target=3D"_blank">RPM resource=
 perl(Net::LDAP)</a></div>
<div id=3D"gmail-m_8863870652701455273LPMetadata_15530072178660.52399545999=
58689" style=3D"margin:10px 0px 16px;color:rgb(102,102,102);font-weight:400=
;font-family:wf_segoe-ui_normal,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,T=
ahoma,Arial,sans-serif;font-size:14px;line-height:14px">
<a href=3D"http://rpmfind.net" target=3D"_blank">rpmfind.net</a></div>
<div id=3D"gmail-m_8863870652701455273LPDescription_15530072178680.08380845=
558096706" style=3D"display:block;color:rgb(102,102,102);font-weight:400;fo=
nt-family:wf_segoe-ui_normal,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Taho=
ma,Arial,sans-serif;font-size:14px;line-height:20px;max-height:100px;overfl=
ow:hidden">
The search service can find package by either name (apache), provides(webse=
rver), absolute file names (/usr/bin/apache), binaries (gprof) or shared li=
braries (libXm ...</div>
</td>
</tr>
</tbody>
</table><br></div></div></div></div></blockquote><div><br></div><div>That r=
pmfind search is a major hint. When setting up rpm spec file Requires or Bu=
ildRequires stanzas for perl modules which require something, you should us=
e that same syntax, rather than a package name. Ex:<br></div><div><br></div=
><div>=C2=A0 =C2=A0=C2=A0Requires: perl(Net::LDAP)</div><div><br></div><div=
>You can specify a version using that syntax as well:</div><div><br></div><=
div>=C2=A0 =C2=A0 Requires: perl(Net::LDAP) &gt;=3D=C2=A00.40</div><div><br=
></div><div>I think this also allows the required module to be installed vi=
a rpm or via a manual install, and the system will go figure it out, but I&=
#39;m not certain of that.</div><div><br></div><div>Fedora RPM guidelines a=
lso mention use of perl(Foo) for requires and provides:=C2=A0<a href=3D"htt=
ps://fedoraproject.org/wiki/Packaging:Perl#Perl_Requires_and_Provides">http=
s://fedoraproject.org/wiki/Packaging:Perl#Perl_Requires_and_Provides</a></d=
iv><div><br></div><div>HTH,</div><div>--<br>Josh I.</div></div></div></div>=
</div></div></div>

--000000000000b039130584a438af--