git: 69c9420a212a - main - news/inn-CURRENT: New port to follow CURRENT snaps

[Kevin Bowling]

On Sat, Jun 12, 2021 at 1:22 AM Alexey Dokuchaev <danfe at freebsd.org> wrote:

> 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.
>

There are several prominent -current ports, so are you proposing yet
another level of mental gymnastics to erase information?  Document rules
and reasons instead of haunting mailing lists.


> > 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.
>

So, it’s ok to obey upstream conventions if they come in large numbers..
sounds like a textbook cargo cult used to bludgeon contributors.


> ./danfe
>