Am Mittwoch, den 28.11.2012, 16:14 +0900 schrieb Jens Petersen: > On 28 November 2012 08:28, Joachim Breitner <[email protected]> wrote: > > Open question: What should GHC on Debian do when building binaries, > > given that all libraries are likely available in both ways – shared or > > static. Shared means that all locally built binaries (e.g. xmonad!) will > > suddenly break when the user upgrades its Haskell packages, as the > > package management is ignorant of unpackaged, locally built programs. > > I’d feel more comfortable if that could not happen. > > Right, I tried patching Fedora's xmonad for a while to use dynamic linking > (it made Mod-q almost instant! :-) but finally reverted it not to confuse > people > linking their .xmonad/ to user libraries, at least until the time > ghc/Cabal support dyn by default...
but would that not mean that when they upgrade a library used by xmonad, their xmonad binary would stop working and they could not even log in any more? It is that kind of breakage that is worrying me. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer [email protected] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [email protected] | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
