Dynamic libraries by default and GHC 7.8
nomeata at debian.org
Wed Nov 28 18:30:52 CET 2012
Am Mittwoch, den 28.11.2012, 11:35 -0500 schrieb Tyson Whitehead:
> > > I was left with the impression that we were going to have this back in
> > > 2010 just as soon as squeeze got out the door... :)
> > It seems that noone cared enough about that, but any help is welcome.
> > Two things to do: Patch haskell-devscripts to build the -dyn ways, and
> > manually adding the additional package stance to the debian/contol files
> > (if it is to be decided that the -dyn libraries should reside in
> > packages of their own. If we decide to include them in the regular
> > packages, this is not needed.)
> Fair enough.
> If I was update my 2010 patch so it worked again at some point in the upcoming
> year (I don't have the time to do this at the moment), would there be a
> reasonable chance it would seem worthwhile to include it at this point?
> Please feel free to say no here if that is the case. I realize that maybe in
> a few years, when there are even more haskell applications, we can revisit the
> again, and possibly then it will make more sense.
there was even a patch? Sorry then, this is not how contributors should
Given that dynamic linking is becoming the default elsewhere, we should
definitely provide it with the next release. So yes, please do look
again at the issue.
We currently have one package providing dynamic libraries, and that is
ghc-dyn. It contains lots of .dyn_hi and some .so files. Which of these
are required at runtime? What is the space ratio between the .dyn_hi
(which presumably are only required at build time) and the .so files? Do
we want separate packages that contain only the files required at
runtime? What should be the filename (just libghc-foo?)? Where do
the .dyn_hi files go? If a user only build dynamically (only staticaly,
both), what packages does she needs?
Make liberal use of package-version-hash-base virtual package names
(e.g. one set of names for the build time requirements with dynamic
packages and one set of names for whats required at runtime) to ensure
that we can revise these decisions without breaking everything.
But this is getting too specific for glasgow-haskell-users, I guess.
replies on this issue please only to d-haskell.
Joachim "nomeata" Breitner
nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the Glasgow-haskell-users