From owner-dev-commits-ports-all@freebsd.org Sat Jun 12 08:22:32 2021 Return-Path: Delivered-To: dev-commits-ports-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A451F64709F; Sat, 12 Jun 2021 08:22:32 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G29gX4FQXz4TlQ; Sat, 12 Jun 2021 08:22:32 +0000 (UTC) (envelope-from danfe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1623486152; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=R7RkzRrAntTq1x1WWL+u6BXI01g4Rx+5V3Vl1kn7T68=; b=VqV1nGDQfGOCpgG0KhVslJQ/k85xzfy82OIXvMQuu0iS6a7oBOg/xUIC4KgvRFeheHUZ2r RhIRFdy0CIC2IudYqKfHXkdBN9WPdfVXcaAou2xspw91d2JsAHzr9Rtok0NUAbyu7aCPev FK0PIpxUmystFRNh2molXOpV0AZ6/q9XXPkszf2Hysf1LmB3HRdPeWnt3VNWfS+K3Y6gel Xc8MpwthZ0RzcnVcMEnf8IKVObS7AaoD9L5uyMUiIQr+WGqz0by5A7EeelZ+EZum/Ev/o4 yJG3SWu9i4BeZV8IWDJlD4VAbqTsyVOyZEE2e6DqR1MsWxbt11HpT9yl8pai0Q== Received: by freefall.freebsd.org (Postfix, from userid 1033) id 83D3E1E3B0; Sat, 12 Jun 2021 08:22:32 +0000 (UTC) Date: Sat, 12 Jun 2021 08:22:32 +0000 From: Alexey Dokuchaev To: Kevin Bowling Cc: Po-Chuan Hsieh , Kevin Bowling , ports-committers , dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 69c9420a212a - main - news/inn-CURRENT: New port to follow CURRENT snaps Message-ID: References: <202106120054.15C0stWJ075154@gitrepo.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1623486152; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=R7RkzRrAntTq1x1WWL+u6BXI01g4Rx+5V3Vl1kn7T68=; b=tmTawiOiN/pqw1OHi2VlsBYIb8cYYHMItISCmkyAI82CgH/Z7ptkAYwTV39b+7wmSssDmI XHqjdSWUOwcF/FyhGOrazghcBBijQwAXtx2sNcKx45CC+q2er44xyecipDSMKbkZ/U8Jlp tyuxiGq8ChK/sM/eg9RtJzlyjQO8qyKcM8VTDqdg7E2Cedc8horx0IkeardLJBXIOuCi99 7gM0rRy124lwVonoXj3aKqQCWqRjJJ/rC0f73pRf4WXT8/AQzkd2TebNOhyOzvoXFBUppi Lm80XseK3pxSEn3zdFj0r2khWcVs4ReG+FfrLkZc/2cZ76rZwGBexV2F2pBXWg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1623486152; a=rsa-sha256; cv=none; b=Gi6x1EKd2UHGUjSNuhlusLpUdVRXD0TfvhTtsPD9Eq1tlIJr4Icjt0DwPxA5POK17pQUSc +u4xg1hdP7jPbUFIMqYXOMIPK3ey6Y5NFzwQkYAEUX9riAM/yd+DEHws3swPqFvAQ92GSl RcL8AKSQADIl4C42dFIaRqu71IPPzGHpuDRrNX6Kw5kKGUuGDbpYKuaFSjEpYBhePrXW4J 0xf4vPMv50yNKLCPtYCVpss7rKBCzqBpuxP+gbpxcI0hpo8jTnmR1IHcMMyCYt3LRH+0oe zC5hvHsJ9C8kO7ouCe91OLkFS0KMc5LXoF51r0BcvGCVvohapfLLsEOumoNAAA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-BeenThere: dev-commits-ports-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the ports repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jun 2021 08:22:32 -0000 On Sat, Jun 12, 2021 at 12:41:14AM -0700, Kevin Bowling wrote: > There's no clear guidance on this kind of thing in the docs, if you > feel this strongly it would be helpful to document it in the handbook. If you ever worked with ports, you could have noticed that we follow `-devel' convention (we currently have over a hundred such ports) and there's not a single example of `-CURRENT' port. > If you look at things like X11 libs, ImageMagick and perl modules > there is no such information erasure, so, why? Things like CPAN packages, Python modules, etc. come in large numbers, have an established naming convention of their own which is also followed by popular GNU/Linux distributions we want to loosely stay consistent with, that's why. But it has nothing to do with how we name unstable/development/snapshot versions of ports and packages. ./danfe