Re: cvs commit: ports/archivers/hs-zip-archive Makefile distinfo pkg-descr pkg-plist ports/devel/hs-binary Makefile distinfo pkg-descr pkg-plist ports/devel/hs-darcs/files patch-Setup.lhs patch-darcs.cabal ports/devel/hs-darcs Makefile distinfo pkg-d

From: Gabor PALI <pgj_at_FreeBSD.org>
Date: Tue, 25 May 2010 01:31:58 +0200
On Tue, May 25, 2010 at 1:16 AM, Dmitry Marakasov <amdmi3_at_amdmi3.ru> wrote:
> That is great - I've played with haskell ports a bit when I was
> porting raincat game ([1]) and had to do hs-sdl, hs-sdl_mixer and
> hs-sdl_image ports (can be found at [2]) as well

I can take a look at them if you want :)


> Back then it really felt like bsd.haskell.mk that does
> all the common stuff for cabal ports would be pretty nice thing

Well, now there is, it is called lang/ghc/bsd.cabal.mk.


> I believe that end-user ports should be named in such a way thay users

I think users of those ports are mostly aware of Cabal and its nature.
 The mentioned ports are also more or less "Haskellish": xmonad can be
configure via writing Haskell code, pandoc works a similar style as
Haskell sources by using the off-side rule, darcs is built upon
"theory of patches".  They assume some awareness of Haskell.

In that sense Agda, alex, happy, c2hs, cpphs, haddock, hmake, hoogle,
hscolour, HaXml, uuagc should be also used without prefixes since they
are "standalone" applications.


> Similar thing happens with python: there are 934 ports that use PYDISTUTILS (thus install
> python modules), however only 630 of them have py- prefix.

I see, thanks for the comments.


> Also, I've just noticed that you've just remved ports at old locations
> and created them at a new ones, while you should'be requested a
> repocopy to not lose all the history.

I think the history should have been preserved, and I asked for a
repocopy in advance...


Cheers,
:g
Received on Mon May 24 2010 - 23:32:00 UTC