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 archives have the pro's
and con's but there were reasons for the choice. It was definitely NOT
arbitrary.
I understand the need for all lower case for *nix systems but isn't the
"build" that one downloads from the "Files" section of Source Forge just
a "container"? Couldn't the "contents" have all lower case names and
wouldn't that meet the *nix requirements? I realize I'm showing my
ignorance here so please help me understand if this is a "must" or just
a "preference".
Gil
On 4/14/2023 7:27 AM, Rony G. Flatscher wrote:
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 all other parts in
lowercase (example -DOS_DIST=centos9 etc) this is a bit odd. I would
like to change this to
set(CPACK_PACKAGE_NAME "oorexx")
Any objections?
Not at all, it seems that all lowercase is the norm on Unix systems
and necessary for distributions. Please go for it!
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
