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
pgj at FreeBSD.org
Thu May 27 10:32:19 UTC 2010
2010/5/27 Alexey Dokuchaev <danfe at freebsd.org>:
> And, equally important, common sense.
It seems our common sense is not common :) But I hope we will reach
> Gabor, I can add little to this thread besides what I've already
> explained about naming ports in our private conversation.
Yes, and you said that rules needs to be bent sometimes.
> I assume that unless strong technical reason
We are importing another namespace here.
> both me and Dmitry would appreciate having them renamed back
You are always referring to the python ports. So I took a look at them:
Install executable(s) but prefixed with "py-":
It is a module but without a "py-" prefix:
No comment :)
Do not get me wrong, I would be happy to revert my changes, but that
would also mean that some Cabal ports will be also failing your
criteria after the change. My problem is that I do not see why only
darcs, pandoc, porte, xmobar and xmonad should omit the "hs-" prefix?
Why not Agda, Agda-executable, alex, brainfuck, c2hs, cpphs, haddock,
happy, hat, HaXml, hdoc, hmake, hoogle, hscolour, idoc, mueval,
texmath, unlambda, uuagc?
To be clear: I feel this distinction very subjective. And in that
sense my subjective (and humble) opinion that they every Hackage port
should have the "hs-" prefix.
Let me make it clear that too: ports in the haskell category and
Haskell Cabal ports are not the same: every Haskell Cabal port is a
Haskell port (i.e. in the "haskell" category), but not every Haskell
port is a Haskell Cabal port. Notable examples: lang/ghc, lang/ohugs,
> All package prefixing should be hidden from our users inside makefiles (of ports and
> supporting infrastructure), not in publicly visible directory names.
Yes, I understand it. My intuitions are just getting clear on the
topic: we want to import another namespace, so we need the "hs-"
prefix to avoid potential clashes.
> After all, simple Unix construct of make "search ... | xargs portupgrade ..." can take care.
> Not to mention that most of just fire up "portupgrade -avi" once in a
Yes, that is true :) I think the problem of updating is not related
to this subject any more, I am convinced in that.
More information about the cvs-all