Date: Wed, 26 May 2010 23:39:43 +0400 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Gabor PALI <pgj@FreeBSD.org> Cc: cvs-ports@freebsd.org, Alexey Dokuchaev <danfe@freebsd.org>, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: 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 Message-ID: <20100526193943.GE25216@hades.panopticon> In-Reply-To: <AANLkTikVxxaDLgEhfblYdix5L0wz1NsRdMO8GC6N0HNi@mail.gmail.com> References: <AANLkTil2ds1NMcOVfF6_R3bCkIb1SPOnLMkagLWt90nk@mail.gmail.com> <20100524220501.GF7380@hades.panopticon> <AANLkTikBXrbZpHaLJN3eVA80RQfJHLOaBLFFK1CNbnh7@mail.gmail.com> <20100525031628.GB8034@FreeBSD.org> <20100526152458.GB25216@hades.panopticon> <AANLkTikVxxaDLgEhfblYdix5L0wz1NsRdMO8GC6N0HNi@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Gabor PALI (pgj@FreeBSD.org) wrote: > > I still disagree with that - prefixes should indicate that the specific > > port is ONLY a module and is used ONLY for development and as a > > dependency - that's pretty clear and useful policy. > > Haskell has its own distribution, we may interpret it as a > distribution within our (ports) distribution. These end-user > applications are just parts of it. That is irrelevant to port naming. > > Thus while leaving PKGNAMEPREFIX=hs- for e.g. darcs, while having the > > port in devel/darcs will ease life for users who want to install it, > > this brings up other problems, such as not seeing expected darcs-X.Y.Z > > in pkg_info and not being able to do `portupgrade darcs-*`, so I really > > think it should not have any prefix at all, along with other end-user > > ports. > > But where is the limit between a development tool and an end-user > application? We might say that every development tool is an end-user > application (for programmers), and every end-user application is a > development tool (for non-programmers). Please do not get me wrong, I > just do not support this way of classification, because it may make > the borders really fuzzy sometimes. If there are executable files, that's an application regardless of to what audience it's targeted (plain users or developers). If there are no executable files, that's a module or library. Prefix is for modules and libraries. If there is, it's an application. > For a Haskell user, it seems exactly the opposite is true: she may get > confused when she tries to find something without an "hs-" prefix. That's not true. At least it was, until these attempts to mark all ports that have something to do with specific language with prefixes - users just know that py- are python modules, p5- are perl modules and hs- are haskell modules. And applications are jsut applications whatever they're written/packaged/distributed with. > However, the virtual category "haskell" may help with this but it is > not visible in the output of pkg-info(1) (or it is?). It is not, however make search cat=haskell does what you want. That is right, you're basically duplicating category in port name. > It also makes the update of the Haskell ports easier (by piggybacking > your example): > > portupgrade hs-* That guarantees nothing. portupgrade -R ghc-* does. > That is why I suggest to "share" popular ports like darcs, pandoc, > xmonad, and xmobar between the two audiences: Haskellers and causal > users of Haskell ports. I do not know how to do this efficiently, > though. We've had these two audiences for years, along with many ports, many languages and many prefixes, and it all worked well with established rule of thumb for using or not using the prefix. It's not a good idea to reinvent new rules and confuse users. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100526193943.GE25216>