Hi Gil,
As Rick has already mentioned it is only the filenames and the top-level
directory name in the source package that is being proposed to be all
lowercase.
The reason for following this convention is that on platforms like
Debian and HomeBrew (one of the the package managers on MacOS),
Gil, the setting he's proposing to change only affects the names of the
built packages, nothing else.
Rick
On Fri, Apr 14, 2023 at 9:03 AM Gilbert Barmwater
wrote:
> I think this needs more discussion before making, what seems on the
> surface to be, a "trivial" change.
>
> When RexxLA received
I think this needs more discussion before making, what seems on the
surface to be, a "trivial" change.
When RexxLA received the source for Object Rexx from IBM, there was
quite a bit of discussion on what the project should be called with the
eventual decision being "ooRexx". I'm sure the arc
On 14.04.2023 09:44, P.O. Jonsson wrote:
While working on creating a source package for #1854 I realized that all our artifacts starts off
with ooRexx-, in CamelFont. It comes from this line in CMakeLists.txt
set(CPACK_PACKAGE_NAME "ooRexx")
Since we have a requirement in the build to keep al
While working on creating a source package for #1854 I realized that all our
artifacts starts off with ooRexx-, in CamelFont. It comes from this line in
CMakeLists.txt
set(CPACK_PACKAGE_NAME "ooRexx")
Since we have a requirement in the build to keep all other parts in lowercase
(example -DOS_
