Re: [arch-haskell] How to update packages in extra?

On 2010/10/18 Rémy Oudompheng
On 2010/10/18 Magnus Therning
wrote: On Mon, Oct 18, 2010 at 14:17, Peter Simons
wrote: Hi,
the PKGBUILD files in "extra" have been generated with ancient versions of cabal2arch, like 0.4.1, and because of that they lack features such as the generation of Haddock reference documentation. Is there any way for us to update those files? Who has the ability to do that?
You'll need an Arch dev to do that. Raise a bug on the bugtracker for the package in question.
I'll do that. Maybe I'll take the opportuniy to add haskell-tar as an official package, since it is a dependency of the archlinux library now.
For the moment I only did mtl, quickcheck and parsec. The packages in [extra] are different from what is output by cabal2arch in the sense that they enable shared libraries, profiling libraries and split-object files. -- Rémy.

On 18/10/10 21:51, Rémy Oudompheng wrote:
On 2010/10/18 Rémy Oudompheng
wrote: On 2010/10/18 Magnus Therning
wrote: On Mon, Oct 18, 2010 at 14:17, Peter Simons
wrote: Hi,
the PKGBUILD files in "extra" have been generated with ancient versions of cabal2arch, like 0.4.1, and because of that they lack features such as the generation of Haddock reference documentation. Is there any way for us to update those files? Who has the ability to do that?
You'll need an Arch dev to do that. Raise a bug on the bugtracker for the package in question.
I'll do that. Maybe I'll take the opportuniy to add haskell-tar as an official package, since it is a dependency of the archlinux library now.
For the moment I only did mtl, quickcheck and parsec. The packages in [extra] are different from what is output by cabal2arch in the sense that they enable shared libraries, profiling libraries and split-object files.
From my Debian days I remember that split-objects could cause problems in some cases, but is there any reason why cabal2arch shouldn't enable shared libs and profiling libs? /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus@therning.org Jabber: magnus@therning.org http://therning.org/magnus identi.ca|twitter: magthe

Hi Magnus,
From my Debian days I remember that split-objects could cause problems in some cases.
do you still remember the problem in a little bit more detail? I am unaware of any problems that split-objects might cause, so I'm curious about this. Split objects have the potential to generate way smaller binaries, so I feel that this feature is highly desirable (for *all* packages, not just those in [extra]).
Is there any reason why cabal2arch shouldn't enable shared libs and profiling libs?
I wouldn't know of any problems, at least not on Linux. In fact, I am all for enabling those features generally in cabal2arch, so that *all* PKGBUILDs we generate have them. Take care, Peter

remyoudompheng:
On 2010/10/18 Rémy Oudompheng
wrote: On 2010/10/18 Magnus Therning
wrote: On Mon, Oct 18, 2010 at 14:17, Peter Simons
wrote: Hi,
the PKGBUILD files in "extra" have been generated with ancient versions of cabal2arch, like 0.4.1, and because of that they lack features such as the generation of Haddock reference documentation. Is there any way for us to update those files? Who has the ability to do that?
You'll need an Arch dev to do that. Raise a bug on the bugtracker for the package in question.
I'll do that. Maybe I'll take the opportuniy to add haskell-tar as an official package, since it is a dependency of the archlinux library now.
For the moment I only did mtl, quickcheck and parsec. The packages in [extra] are different from what is output by cabal2arch in the sense that they enable shared libraries, profiling libraries and split-object files.
That's weird. Why would they do that? Better to have cabal2arch generate PKGBUILDs that do all that. -- Don
participants (4)
-
Don Stewart
-
Magnus Therning
-
Peter Simons
-
Rémy Oudompheng