Hi Michael & Martin,
On 2013-03-11 Michael Davidsaver wrote:
>
> The added dependency is caused by a change I made to where libCap5.so is
> installed for the 3.14.12 series. Previously if was installed in
> /usr/lib/epics/lib, now it is under /usr/share/perl5 (I'll check, but I
> think it should actually be in /usr/lib/perl5).
You almost certainly won't be able to use a libCap5.so that was built against
Perl 5.10 on Perl 5.14. I introduced the Perl version number and architecture
into the path to libCap5.so to allow different Perl versions and architectures
to coexist in the same install directory.
> So avoiding the perlapi-* dep for epics-dev means moving (or removing)
> these scripts. My current plan is to move CA.pm, libCap5.so, and the
> scripts which use them to a separate binary package. Thoughts?
Sounds like a good idea. The Perl5 major version number matters for this
package, and it sounds like you might have to have more than one version of
that package available for install depending on which Perl5 version is in use
on the system — I would hope that dpkg can do something like that.
- Andrew
--
There is no such thing as a free lunch. When invited for lunch,
it is best to check if you are there to eat, or to be eaten.
-- Clive Robinson
- Replies:
- Re: epics-perl & perlapi-5.10.1 Martin Konrad
- References:
- epics-perl & perlapi-5.10.1 Martin Konrad
- Re: epics-perl & perlapi-5.10.1 Michael Davidsaver
- Navigate by Date:
- Prev:
Re: EDM Text Control Widget Motif behavior Isadoro Carlino
- Next:
Save and Restore parameters Julio Calvo
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: epics-perl & perlapi-5.10.1 Michael Davidsaver
- Next:
Re: epics-perl & perlapi-5.10.1 Martin Konrad
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|