Re: Bug#770376: Allow rpaths in /usr/lib/ghc/
On Sat, Nov 22, 2014 at 12:29 PM, Joachim Breitner <nomeata@debian.org> wrote:
> Hi,
>
>
> Am Freitag, den 21.11.2014, 19:22 +0100 schrieb Niels Thykier:
>> 1. Could you explain how can I detect ghc package ?
>
> They are usually named "libghc-.*-dev", but I think it is safer to match
> on the target of the rpath: If it is in /usr/lib/ghc/, it is ok.
>
>> 2. Could you pin point to some documentation about this shared library
>> stuff ?
>
> http://www.haskell.org/ghc/docs/latest/html/users_guide/using-shared-libs.html#finding-shared-libs-unix
>
>
>> 3. Could you explain why rpath and improve wiki
>> (https://wiki.debian.org/RpathIssue) particularly with the issue here
>> does not apply in your case.
>
> Because I believe this falls under the exception
>
> Currently, the only generally accepted use of this feature in
> Debian is to add non-standard library path
> (like /usr/lib/<package>) to libraries that are only intended to
> be used by the executables or other libraries within the same
> source package.
>
> with the small twist that they are not all built from the same source
> package, but in all cases it is the single "ghc" package that decides on
> these locations and handles the rpaths.
I do ot understand this part. it is ld.so that found library.
So if so library change package during upgrade you are burned. Why do
you use the deploy mode ?
Bastien
> I can amend the wiki once a decision has been made.
>
>
> Greetings,
> Joachim
>
> --
> Joachim "nomeata" Breitner
> Debian Developer
> nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
> JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
>
Reply to: