Charles Fry <[EMAIL PROTECTED]> writes:
>> So please, please, please do fix (remove) the rpath in the package.
>
> I would appreciate any tips on how to go about fixing this. My package
> is courierpassd, currently only available in unstable. It depends on
> courier-authlib which currently uses /u
On Fri, Jul 14, 2006 at 09:57:26AM -0400, Charles Fry wrote:
> > So please, please, please do fix (remove) the rpath in the package.
>
> I would appreciate any tips on how to go about fixing this. My package
> is courierpassd, currently only available in unstable. It depends on
> courier-authlib w
> So please, please, please do fix (remove) the rpath in the package.
I would appreciate any tips on how to go about fixing this. My package
is courierpassd, currently only available in unstable. It depends on
courier-authlib which currently uses /usr/lib/courier-authlib. I can't
figure out how to
Bas Wijnen <[EMAIL PROTECTED]> writes:
> On Wed, Jul 12, 2006 at 05:32:12PM -0400, Charles Fry wrote:
>> > > > Depends. Does it actually fix the warning?
>> > >
>> > > Yes, but it also broke my binary, which can no longer find the needed
>> > > library. Any suggestions? Is rpath okay in this case
On Thu, Jul 13, 2006 at 09:40:23AM -0400, Charles Fry wrote:
> > In almost any situation rpath is a bad thing. It is a very good idea to
> > let lintian check this. A "private" library for the package is an
> > exception. Of course lintian could also check and allow
> > /usr/lib/$packagename wit
> In almost any situation rpath is a bad thing. It is a very good idea to let
> lintian check this. A "private" library for the package is an exception. Of
> course lintian could also check and allow /usr/lib/$packagename without a
> warning. However, the rpath check is useful in general, becau
On Wed, Jul 12, 2006 at 05:32:12PM -0400, Charles Fry wrote:
> > > > Depends. Does it actually fix the warning?
> > >
> > > Yes, but it also broke my binary, which can no longer find the needed
> > > library. Any suggestions? Is rpath okay in this case? The needed library
> > > is coming from /usr
Felipe Sateler <[EMAIL PROTECTED]> writes:
> Charles Fry wrote:
>> I finally found some pseudo-official documentation on this:
>>
>>http://wiki.debian.org/RpathIssue
>>
>> which confirms what you said:
>>
>>"Currently, the only valid use of this feature in Debian is to add
>>non-sta
Charles Fry wrote:
> I finally found some pseudo-official documentation on this:
>
>http://wiki.debian.org/RpathIssue
>
> which confirms what you said:
>
>"Currently, the only valid use of this feature in Debian is to add
>non-standard library path (like /usr/lib/) to libraries tha
> > So is the lintian test wrong? Should it only be checking for rpaths that
> > aren't system directories?
>
> good question!
I finally found some pseudo-official documentation on this:
http://wiki.debian.org/RpathIssue
which confirms what you said:
"Currently, the only valid use of thi
On Wed, Jul 12, 2006 at 05:32:12PM -0400, Charles Fry wrote:
> So is the lintian test wrong? Should it only be checking for rpaths that
> aren't system directories?
good question!
--
Rodrigo Gallardo
GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28
signature.asc
Description:
> > > Depends. Does it actually fix the warning?
> >
> > Yes, but it also broke my binary, which can no longer find the needed
> > library. Any suggestions? Is rpath okay in this case? The needed library
> > is coming from /usr/lib/courier-authlib.
>
> In this case, I believe it is correct. rpath
On Wed, Jul 12, 2006 at 05:05:36PM -0400, Charles Fry wrote:
> > > So, my questions are: Have I succesfully identified the currently
> > > accepted ways of fixing this warning?
> >
> > Depends. Does it actually fix the warning?
>
> Yes, but it also broke my binary, which can no longer find the n
On Wed, Jul 12, 2006 at 09:58:25PM +0100, Neil Williams wrote:
> Charles Fry wrote:
> >
> > A package I am creating from scratch is giving me the lintian warning
> > binary-or-shlib-defines-rpath.
>
> I've looked for this kind of answer before - it's not as simple as it
> appears. rpath arises fr
> I've looked for this kind of answer before - it's not as simple as it
> appears. rpath arises from libraries in non-standard locations, either
> alone or when linked to a binary.
>
> 1. Dependencies can bring in rpath: See Bug # 374797 (amd64 specific)
> 2. linking binaries against pkglib_LTLIBR
Charles Fry wrote:
>
> A package I am creating from scratch is giving me the lintian warning
> binary-or-shlib-defines-rpath.
I've looked for this kind of answer before - it's not as simple as it
appears. rpath arises from libraries in non-standard locations, either
alone or when linked to a bina
Hi,
A package I am creating from scratch is giving me the lintian warning
binary-or-shlib-defines-rpath. lintian-info in turn tells me "Please
contact debian-devel@lists.debian.org if you have questions about this."
My search revealed two possible solutions: 'configure --disable-rpath'
where supp
17 matches
Mail list logo
