Let me try again. When a user wants to install ooRexx on his platform,
he goes to SF and looks in the Files section under the ooRexx tab for
the most recent file with a name that matches his platform, downloads it
and uses the appropriate installation mechanism for that platform. I
was just suggesting that if we know how to name that file for the
platform for which it is intended, we might make the executable be able
to also know (and supply) that information. The programmer/testcase
writer could then tailor his program to behave appropriately for that
platform if necessary. FWIW
On 2/16/2019 2:53 PM, Enrico Sorichetti via Oorexx-devel wrote:
something built on a certain a platform WILL NOT run on a different one
LINUX will be even more selective
There are subtle differences between the different distributions
And there are also common practices to deal with …
xxxxxx.deb is likely a package for Debian family system
xxxxx.rpm is the same for red hat family systems
The package type is usually a good hint on the distribution it might
run on
E
On 16 Feb 2019, at 20:37, Rick McGuire <object.r...@gmail.com
<mailto:object.r...@gmail.com>> wrote:
That’s only the platform it was built on, not necessarily the one
it’s running on.
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
