From owner-cvs-all@FreeBSD.ORG Wed May 26 20:03:18 2010 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9362B1065687; Wed, 26 May 2010 20:03:18 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 91FBC8FC08; Wed, 26 May 2010 20:03:17 +0000 (UTC) Received: by fxm12 with SMTP id 12so89981fxm.13 for ; Wed, 26 May 2010 13:03:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=rRVox08LkfOpLYG5hp5PZD/PKp58iAd65/QBgSGJ9Nk=; b=ppsX+mBUoOsgRt7xcuD/nGcUPVRdHK0kkMYkVLBd7/BjqNpO+Ark8itKypIiAVdyRv c7vxGWdVO2Ztik6Fz3ymdtURBBm6RqDKd0eThmfeuXLF4pf12Jl1ngJZLksBP8nnZt+L m1jLjZw/hYoFZI+v5KBw6+yMz6yfwyAzjk54Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=mfONjCO64LMY/zeLO83J6UfQ+jTvOkTh/T3bpmUzpCgxbq0S9nDjFpkU0z8vyA0Z/U d2fWQT3c5O+dCKdH8SWP4DIroz2wnIkhY2jP5ckvhxU2pPHVM/EB20NW27Ij1m8beTH7 kEbQQTCrGSAnevI5m0VhSYZQjUBkD3IHbTQoY= MIME-Version: 1.0 Received: by 10.223.63.76 with SMTP id a12mr8189540fai.10.1274904195362; Wed, 26 May 2010 13:03:15 -0700 (PDT) Sender: pali.gabor@googlemail.com Received: by 10.223.120.129 with HTTP; Wed, 26 May 2010 13:03:15 -0700 (PDT) In-Reply-To: <20100526193943.GE25216@hades.panopticon> References: <20100524220501.GF7380@hades.panopticon> <20100525031628.GB8034@FreeBSD.org> <20100526152458.GB25216@hades.panopticon> <20100526193943.GE25216@hades.panopticon> Date: Wed, 26 May 2010 22:03:15 +0200 X-Google-Sender-Auth: NLmlrCOiTRfxjFO5VroI0Xd72x8 Message-ID: From: Gabor PALI To: Dmitry Marakasov Content-Type: text/plain; charset=ISO-8859-1 Cc: cvs-ports@freebsd.org, Alexey Dokuchaev , 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 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: **OBSOLETE** CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 May 2010 20:03:18 -0000 On Wed, May 26, 2010 at 9:39 PM, Dmitry Marakasov wrote: > That is irrelevant to port naming. Understood. > 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. What if there is both? Even worse: what if the executable is just an option (see archivers/hs-zip-archive) or it can installed as a library or as an executable or both (textproc/(hs-)pandoc)? Most Haskell applications has their own libraries which might be used by another applications (see textproc/(hs-)pandoc). > 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. I see. > That guarantees nothing. > portupgrade -R ghc-* does. I think no. Sorry, I do not know portupgrade, so I have to branch my answer: - If -R use build dependency for tracking updates: GHC is not updated as frequently (ab. twice a year) as its dependent ports, so this seems like exploiting a side-effect of portupgrade. - If -R use run dependency for tracking updates: It will not update standalone Haskell applications, because theoretically they should not depend on GHC (practically they depend at the moment but without an exact reason), since GHC is effectively required at compile-time. > 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. Oh, good to know. Can you give me a pointer to this rule of thumb? > It's not a good idea to reinvent new rules and confuse users. They did not seem to be confused, I have not got any complaints so far. I do not want to reinvent anything, I just need some clarification here because I do not see it logical. Thank you for explaining me the well-established concepts. Cheers, :g