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

[Alexey Dokuchaev]

On Wed, May 26, 2010 at 09:43:24PM +0200, Gabor Pali wrote:
> I think you are expecting something like that: the User wants to
> install darcs, so the User tries to find out what it can be found.
> "Oh, it must be a development tool, so it must be the devel category.
> Oh, it is called darcs, so it must be in the darcs directory."  It
> covers a nice approach: make the layout consist with the user's
> intuition.  If this is your intention I agree with it.  But.  What may
> happen in case of a Haskell user?  "Oh, it is a Haskell tool, so it
> must be in the haskell category.  Oh, it is a Cabal hackage, so it
> must be prefixed with `hs-` like all the other Haskell ports in the
> tree.  But there is neither (real) haskell directory nor hs-darcs in
> the ports tree.  Where can it be?"

The answer is simple and literally the same as you described for
devel/darcs (in terms of reasoning behind category and name); you've
just skipped a step in case of Haskell user:

Oh, it is a Cabal hackage, so it must be prefixed with `hs-' like all
the other Haskell ports in the tree.  But actually, we do not prefix
ports, we do sometimes prefix packages.  Oh, right.  So it is simply
"devel/darcs" then.  Makes sense.  :-)

./danfe





But there is neither (real) haskell directory nor hs-darcs in
> the ports tree.  Where can it be?