Date: Sat, 12 Jun 2021 08:22:32 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Kevin Bowling <kevin.bowling@kev009.com> Cc: Po-Chuan Hsieh <sunpoet@freebsd.org>, Kevin Bowling <kbowling@freebsd.org>, ports-committers <ports-committers@freebsd.org>, 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: <YMRuyKDxUlESzror@FreeBSD.org> In-Reply-To: <CAK7dMtA1wH3kAnYsobpZFr0orLYWgsLxDgXL2cHOr9DLxJt1xg@mail.gmail.com> References: <202106120054.15C0stWJ075154@gitrepo.freebsd.org> <CAMHz58Qj0-zMocZw0WFVJzQvfSrfaY=cK%2BUnauiU==4kKE1zMQ@mail.gmail.com> <CAK7dMtA1wH3kAnYsobpZFr0orLYWgsLxDgXL2cHOr9DLxJt1xg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YMRuyKDxUlESzror>