misc/54657: releasedir from evbarm "build.sh release" differs from ftp.netbsd.org

[gson%gson.org@localhost (Andreas Gustafsson)]

>Number:         54657
>Category:       misc
>Synopsis:       releasedir from evarm "build.sh release" differs from ftp.netbsd.org
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 29 16:05:00 +0000 2019
>Originator:     Andreas Gustafsson
>Release:        NetBSD-current
>Organization:

>Environment:
System: NetBSD
Architecture: arm
Machine: evbarm
>Description:

One might think that "build.sh release" or "make release" would
produce a releasedir with the same directory layout as the official
releases on ftp.netbsd.org, but for the various evbarm ports, this is
not the case.

Specifically, the release directory on ftp.netbsd.org has
subdirectories such as "evbarm-earmv7hf" and "evbarm-aarch64", but if
you run "build.sh release" yourself, the corresponding directory will
be called just "evbarm".

This causes complications for automated testing because you can't use
the same subdirectory when testing a local build as when testing an
official release, and in the case of a local build, you can't deduce
the port from the directory name.

Also, like PR 54544, it means that not all the code needed to fully
reproduce a NetBSD release is open source.

>How-To-Repeat:

>Fix:

Move the code to generate the unique subdirectory names used by the
official releases from localsrc to src/build.sh.

Who even has the authority to "declassify" non-public code like that?
Releng?  Core?  The board?