Re: [Oorexx-devel] Changes in rev 12051

2020-04-13 Thread Erich Steinböck 
>
> Don't you also have to ensure rxapi is stopped/started when switching
> between different versions?
>

I guess you're right. Sure, I have my killrxapi batch file available all
the time, but I really almost never (have to) use it.
That may be because there's only very little change happening with rxapi,
an/or because each interpreter build always kills off rxapi.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-13 Thread Gil Barmwater 
Don't you also have to ensure rxapi is stopped/started when switching 
between different versions?


Gil

On 4/12/2020 6:35 AM, Erich Steinböck wrote:


provide Linux installers for an *alternative installation
location* for those who really need it, say to /opt or /usr/local/
rather than to /usr?

While I agree that our installers should not install to /usr but to 
/usr/local instead (which I think was what Enrico suggests and what 
CMake GNU default is), I don't want to have to provide multiple 
installers.
Anyone who needs an installer for /opt can always build with 
-DCMAKE_INSTALL_PREFIX=/opt/oorexx or such.


 juggling several rexx installations: how is it done on the
Windows platform? 

I have set up a bunch of aliases (set with doskey 
/macrofile=doskey.mac in a profile.bat which runs when starting a 
Command Prompt) like rexx4 or rexx5r or rexx532d pointing to various 
rexx.exe builds, and a bat file rexx5rev.bat which allows me to run 
rexx.exe from a choice of saved build revisions.
No additional setup is required, these build (or saved) paths don't 
have to be in PATH .. when searching for its associated files, the 
interpreter will look first in the same directory as the executable.



___
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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-12 Thread Erich Steinböck 
>
> provide Linux installers for an *alternative installation location* for
> those who really need it, say to /opt or /usr/local/ rather than to /usr?
>
While I agree that our installers should not install to /usr but to
/usr/local instead (which I think was what Enrico suggests and what CMake
GNU default is), I don't want to have to provide multiple installers.
Anyone who needs an installer for /opt can always build with
-DCMAKE_INSTALL_PREFIX=/opt/oorexx or such.

 juggling several rexx installations: how is it done on the Windows
> platform?

I have set up a bunch of aliases (set with doskey /macrofile=doskey.mac in
a profile.bat which runs when starting a Command Prompt) like rexx4 or
rexx5r or rexx532d pointing to various rexx.exe builds, and a bat file
rexx5rev.bat which allows me to run rexx.exe from a choice of saved build
revisions.
No additional setup is required, these build (or saved) paths don't have to
be in PATH .. when searching for its associated files, the interpreter will
look first in the same directory as the executable.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-11 Thread P.O. Jonsson 
I just wanted to sum this point up (rollback of update-alternatives in 1250 and 
12051):

I found the reason why I could not replace newer build with older ones on 
CentOS and fixed it. I can now reproduce what Enrico also confirmed. I can 
install/uninstall/reinstall any version of ooRexx from 12050 to the current 
12058.

However, trying to install any version prior to 12050 fail. The installation of 
for instance 12038 will go through without any error messages but rexx -v will 
consistently refer to the last install (the install with the highest revision 
number). I have tried it on 3 different .rpm builds and 3 different .deb builds 
and the behavior is the same so I think it is not just me. As a consequence it 
is no longer possible to go back to a version of ooRexx containing the 
rexx-oorexx update-alternatives solution. Further In 12058 I restored some 
variables needed in the installer that were removed by the rollback. The 
package on CentOS is now correctly indicating the revision number which it did 
not do in 12057.

I propose another solution to the update-alternatives problem: Why not provide 
Linux installers for an alternative installation location for those who really 
need it, say to /opt or /usr/local/ rather than to /usr? Such an installation 
would be active only after amending the path, something that could be arranged 
with a shell script. Most Slaves on Jenkins are dormant 90-95% of the time so 
there is capacity for building them.

I also have a question to those juggling several rexx installations: how is it 
done on the Windows platform?

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 08.04.2020 um 16:34 schrieb Erich Steinböck :
> 
> Try installing an older build (rpm module) after removing the newer build
> I don't think I can as the two RPM-based slaves CentOS and SLES390 I have 
> access to don't have full sudo access.
> 
> Enrico, can you maybe test what P.O. asks for?
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-09 Thread P.O. Jonsson 

> Am 09.04.2020 um 00:01 schrieb Rick McGuire :
> 
> 
> This was a change on my proposal, ooRexx5.0.0 is somewhat over specified and 
> will be incorrect as soon as ooRexx 5.0.1 arrives. ooRexx5 is sufficient to 
> separate it from ooRexx 4.
> 
> this should probably be at least 2 digits, as a 5.1.0 release would mean 
> there are new features that are not in 5.0.x.  
> 

I disagree. On Windows the installation is referred to as a folder "Open Object 
Rexx“ and the installation itself resides in C:\Program Files\ooRexx or 
C:\Program Files (x86)\ooRexx as the case may be. On Linux it goes straight 
into /usr/bin.

There is thus no reason to over-specify the installation on macOS, in 
particular since there are NO dependencies outside of the bundle on macOS. 
Installing 5.1.0 after having 5.0.0 only mean to overwrite an existing bundle 
with the new one.

Anyone with the need to keep both can rename the bundle manually or keep them 
in different places. Vanilla user will just replace the old with the new. 

/PO___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Rick McGuire 
On Wed, Apr 8, 2020 at 5:47 PM P.O. Jonsson  wrote:

> Dear René,
>
> This was a change on my proposal, ooRexx5.0.0 is somewhat over specified
> and will be incorrect as soon as ooRexx 5.0.1 arrives. ooRexx5 is
> sufficient to separate it from ooRexx 4.
>

this should probably be at least 2 digits, as a 5.1.0 release would mean
there are new features that are not in 5.0.x.

>
> If you try one of the dmg installers I have built here
>  
> you
> can actually just double click the dmg and then drag the entire „app“ to
> wherever you want it, the installation bundle appears as a single file on
> macOS.
>
> The latest installers also include the PDF documentation btw.
>
> The default installation to ~/Applications poses two problems:
>
> 1: ~/Applications does not exist on a freshly installed macOS
>
> 2: The user needs to amend the path to make the installation fly.
>
> 
>
> Problem 1 goes away with an install to /Applications instead of
> ~/Applications
>
> Since the installation is atomic it can be dragged to the bin so there is
> no uninstall process necessary.
>
> And, I just checked - you do not need elevated rights to install into
> /Applications
>
> Just an idea…
>
> 
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 08.04.2020 um 23:13 schrieb René Jansen :
>
> I have funny stuff going on also: my MacOSX build kept telling me that it
> was from June 2019 (which might be the last time I built on this particular
> mac).
> Checking up on it, I found that it now installs in ~/Applications/ooRexx5
> instead of ~/Applications/ooRexx5.0.0
>
> No big deal but a tad surprising.
>
> René.
>
> On 8 Apr 2020, at 18:04, P.O. Jonsson  wrote:
>
> @Enrico: did you use the rexx -v to confirm the version? For both versions?
>
> If so I have a rotten build :-(
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 08.04.2020 um 17:48 schrieb Enrico Sorichetti via Oorexx-devel <
> oorexx-devel@lists.sourceforge.net>:
>
> Going back and forth between builds 12050 and 12054
> Did not cause any problems  on centos 8
>
> Also using the —replacefiles clause lets You install over an existing
> installation without uninstalling  the previous one
>
> After that the rpm -e must be qualified
> And uninstalling the older only cleanups the rpm/dnf install database
> And leaves a working rexx
>
> enrico
>
>
> On 8 Apr 2020, at 16:34, Erich Steinböck 
> wrote:
>
> Try installing an older build (rpm module) after removing the newer build
>
> I don't think I can as the two RPM-based slaves CentOS and SLES390 I have
> access to don't have full sudo access.
>
> Enrico, can you maybe test what P.O. asks for?
> ___
> 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
>
>
> ___
> 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
>
>
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread René Jansen 
Ah ok - that is fine with me.

René.

> On 8 Apr 2020, at 23:46, P.O. Jonsson  wrote:
> 
> Dear René,
> 
> This was a change on my proposal, ooRexx5.0.0 is somewhat over specified and 
> will be incorrect as soon as ooRexx 5.0.1 arrives. ooRexx5 is sufficient to 
> separate it from ooRexx 4.
> 
> If you try one of the dmg installers I have built here 
>  
> you can actually just double click the dmg and then drag the entire „app“ to 
> wherever you want it, the installation bundle appears as a single file on 
> macOS.
> 
> The latest installers also include the PDF documentation btw. 
> 
> The default installation to ~/Applications poses two problems:
> 
> 1: ~/Applications does not exist on a freshly installed macOS
> 
> 2: The user needs to amend the path to make the installation fly.
> 
> 
> 
> Problem 1 goes away with an install to /Applications instead of ~/Applications
> 
> Since the installation is atomic it can be dragged to the bin so there is no 
> uninstall process necessary.
> 
> And, I just checked - you do not need elevated rights to install into 
> /Applications
> 
> Just an idea…
> 
> 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
>> Am 08.04.2020 um 23:13 schrieb René Jansen > >:
>> 
>> I have funny stuff going on also: my MacOSX build kept telling me that it 
>> was from June 2019 (which might be the last time I built on this particular 
>> mac).
>> Checking up on it, I found that it now installs in ~/Applications/ooRexx5 
>> instead of ~/Applications/ooRexx5.0.0
>> 
>> No big deal but a tad surprising.
>> 
>> René.
>> 
>>> On 8 Apr 2020, at 18:04, P.O. Jonsson >> > wrote:
>>> 
>>> @Enrico: did you use the rexx -v to confirm the version? For both versions?
>>> 
>>> If so I have a rotten build :-(
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
 Am 08.04.2020 um 17:48 schrieb Enrico Sorichetti via Oorexx-devel 
 >>> >:
 
 Going back and forth between builds 12050 and 12054 
 Did not cause any problems  on centos 8
 
 Also using the —replacefiles clause lets You install over an existing 
 installation without uninstalling  the previous one
 
 After that the rpm -e must be qualified  
 And uninstalling the older only cleanups the rpm/dnf install database
 And leaves a working rexx
 
 enrico
 
 
> On 8 Apr 2020, at 16:34, Erich Steinböck  > wrote:
> 
> Try installing an older build (rpm module) after removing the newer build
> I don't think I can as the two RPM-based slaves CentOS and SLES390 I have 
> access to don't have full sudo access.
> 
> Enrico, can you maybe test what P.O. asks for?
> ___
> 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 
 
>>> 
>>> ___
>>> 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
> 
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson 
Dear René,

This was a change on my proposal, ooRexx5.0.0 is somewhat over specified and 
will be incorrect as soon as ooRexx 5.0.1 arrives. ooRexx5 is sufficient to 
separate it from ooRexx 4.

If you try one of the dmg installers I have built here 
 you 
can actually just double click the dmg and then drag the entire „app“ to 
wherever you want it, the installation bundle appears as a single file on macOS.

The latest installers also include the PDF documentation btw. 

The default installation to ~/Applications poses two problems:

1: ~/Applications does not exist on a freshly installed macOS

2: The user needs to amend the path to make the installation fly.



Problem 1 goes away with an install to /Applications instead of ~/Applications

Since the installation is atomic it can be dragged to the bin so there is no 
uninstall process necessary.

And, I just checked - you do not need elevated rights to install into 
/Applications

Just an idea…



Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 08.04.2020 um 23:13 schrieb René Jansen :
> 
> I have funny stuff going on also: my MacOSX build kept telling me that it was 
> from June 2019 (which might be the last time I built on this particular mac).
> Checking up on it, I found that it now installs in ~/Applications/ooRexx5 
> instead of ~/Applications/ooRexx5.0.0
> 
> No big deal but a tad surprising.
> 
> René.
> 
>> On 8 Apr 2020, at 18:04, P.O. Jonsson > > wrote:
>> 
>> @Enrico: did you use the rexx -v to confirm the version? For both versions?
>> 
>> If so I have a rotten build :-(
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>>> Am 08.04.2020 um 17:48 schrieb Enrico Sorichetti via Oorexx-devel 
>>> >> >:
>>> 
>>> Going back and forth between builds 12050 and 12054 
>>> Did not cause any problems  on centos 8
>>> 
>>> Also using the —replacefiles clause lets You install over an existing 
>>> installation without uninstalling  the previous one
>>> 
>>> After that the rpm -e must be qualified  
>>> And uninstalling the older only cleanups the rpm/dnf install database
>>> And leaves a working rexx
>>> 
>>> enrico
>>> 
>>> 
 On 8 Apr 2020, at 16:34, Erich Steinböck >>> > wrote:
 
 Try installing an older build (rpm module) after removing the newer build
 I don't think I can as the two RPM-based slaves CentOS and SLES390 I have 
 access to don't have full sudo access.
 
 Enrico, can you maybe test what P.O. asks for?
 ___
 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 
>>> 
>> 
>> ___
>> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread René Jansen 
I have funny stuff going on also: my MacOSX build kept telling me that it was 
from June 2019 (which might be the last time I built on this particular mac).
Checking up on it, I found that it now installs in ~/Applications/ooRexx5 
instead of ~/Applications/ooRexx5.0.0

No big deal but a tad surprising.

René.

> On 8 Apr 2020, at 18:04, P.O. Jonsson  wrote:
> 
> @Enrico: did you use the rexx -v to confirm the version? For both versions?
> 
> If so I have a rotten build :-(
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
>> Am 08.04.2020 um 17:48 schrieb Enrico Sorichetti via Oorexx-devel 
>> > >:
>> 
>> Going back and forth between builds 12050 and 12054 
>> Did not cause any problems  on centos 8
>> 
>> Also using the —replacefiles clause lets You install over an existing 
>> installation without uninstalling  the previous one
>> 
>> After that the rpm -e must be qualified  
>> And uninstalling the older only cleanups the rpm/dnf install database
>> And leaves a working rexx
>> 
>> enrico
>> 
>> 
>>> On 8 Apr 2020, at 16:34, Erich Steinböck >> > wrote:
>>> 
>>> Try installing an older build (rpm module) after removing the newer build
>>> I don't think I can as the two RPM-based slaves CentOS and SLES390 I have 
>>> access to don't have full sudo access.
>>> 
>>> Enrico, can you maybe test what P.O. asks for?
>>> ___
>>> 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
> 
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson 
@Enrico: did you use the rexx -v to confirm the version? For both versions?

If so I have a rotten build :-(

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 08.04.2020 um 17:48 schrieb Enrico Sorichetti via Oorexx-devel 
> :
> 
> Going back and forth between builds 12050 and 12054 
> Did not cause any problems  on centos 8
> 
> Also using the —replacefiles clause lets You install over an existing 
> installation without uninstalling  the previous one
> 
> After that the rpm -e must be qualified  
> And uninstalling the older only cleanups the rpm/dnf install database
> And leaves a working rexx
> 
> enrico
> 
> 
>> On 8 Apr 2020, at 16:34, Erich Steinböck > > wrote:
>> 
>> Try installing an older build (rpm module) after removing the newer build
>> I don't think I can as the two RPM-based slaves CentOS and SLES390 I have 
>> access to don't have full sudo access.
>> 
>> Enrico, can you maybe test what P.O. asks for?
>> ___
>> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Enrico Sorichetti via Oorexx-devel 
Going back and forth between builds 12050 and 12054 
Did not cause any problems  on centos 8

Also using the —replacefiles clause lets You install over an existing 
installation without uninstalling  the previous one

After that the rpm -e must be qualified  
And uninstalling the older only cleanups the rpm/dnf install database
And leaves a working rexx

enrico


> On 8 Apr 2020, at 16:34, Erich Steinböck  wrote:
> 
> Try installing an older build (rpm module) after removing the newer build
> I don't think I can as the two RPM-based slaves CentOS and SLES390 I have 
> access to don't have full sudo access.
> 
> Enrico, can you maybe test what P.O. asks for?
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson 
All my local builds are here 


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 08.04.2020 um 16:34 schrieb Erich Steinböck :
> 
> Try installing an older build (rpm module) after removing the newer build
> I don't think I can as the two RPM-based slaves CentOS and SLES390 I have 
> access to don't have full sudo access.
> 
> Enrico, can you maybe test what P.O. asks for?
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Erich Steinböck 
>
> Try installing an older build (rpm module) after removing the newer build

I don't think I can as the two RPM-based slaves CentOS and SLES390 I have
access to don't have full sudo access.

Enrico, can you maybe test what P.O. asks for?
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread P.O. Jonsson 
Hi,

It works just fine for me as well to replace and OLDER version with a NEWER 
version incrementally (this is what the Jenkins slaves do as well). Furthermore 
building from source and installing always work, irrespective of version. The 
problem only surfaces when you use and older rpm module after having 
uninstalled a newer one.

Try installing an older build (rpm module) after removing the newer build and 
see if it is the same for you, if not my Centos and Fedora setups have a 
problem.

How does one completely remove an older build? I used dnf remove. Is there a 
way to completely wipe out older builds?

I will try to make a fresh install and see if that works.

PS some of the lines removed by your change need to go back in again, I will 
provide them later (version number of package is distorted currently) 

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 08.04.2020 um 15:58 schrieb Erich Steinböck :
> 
> Hi P.O., you may have copies of old builds hanging around, or build from an 
> outdated SVN working copy.
> 
> Our build machine builds fine on all slaves, including the CentOS slave, and 
> uploads packages with the correct SVN build numbers.
> (see the console log of the sourceforge-upload job).
> 
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-08 Thread Erich Steinböck 
Hi P.O., you may have copies of old builds hanging around, or build from an
outdated SVN working copy.

Our build machine builds fine on all slaves, including the CentOS slave,
and uploads packages with the correct SVN build numbers.
(see the console log of the sourceforge-upload job).
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-07 Thread P.O. Jonsson 
Compare to this, this is really weird (my highlighting)

[osboxes@fedora31 ~]$ rexx -v
Open Object Rexx Version 5.0.0 r12054
Build date: Apr  7 2020
Addressing mode: 64
Copyright (c) 1995, 2004 IBM Corporation. All rights reserved.
Copyright (c) 2005-2020 Rexx Language Association. All rights reserved.
This program and the accompanying materials are made available under the terms
of the Common Public License v1.0 which accompanies this distribution or at
http://www.oorexx.org/license.html 

[osboxes@fedora31 ~]$ sudo dnf remove ooRexx
[sudo] password for osboxes:
Dependencies resolved.

 PackageArchitecture   Version Repository Size

Removing:
 ooRexx x86_64 5.0.0-11949 @@commandline 6.1 M

Transaction Summary

Remove  1 Package


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 07.04.2020 um 19:21 schrieb P.O. Jonsson :
> 
>> 
>> The thing with not being able to revert to an older version of ooRexx is a 
>> murkier business. I do not think it is related to this change, I just had 
>> not noticed since I always build a newer version.
>> 
> 
> This is a just a thought, but is there ANY possibility that rexx -v  reports 
> the wrong version due to some unfortunate cashing? When removing one version 
> and installing another? The problem is the same on Fedora (both rpm builds), 
> it will keep the highest number (or the first number , not sure).
> 
> Any idea on how to confirm/reject this hypothesis?
> ___
> 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

Re: [Oorexx-devel] Changes in rev 12051

2020-04-07 Thread P.O. Jonsson 
> 
> The thing with not being able to revert to an older version of ooRexx is a 
> murkier business. I do not think it is related to this change, I just had not 
> noticed since I always build a newer version.
> 

This is a just a thought, but is there ANY possibility that rexx -v  reports 
the wrong version due to some unfortunate cashing? When removing one version 
and installing another? The problem is the same on Fedora (both rpm builds), it 
will keep the highest number (or the first number , not sure).

Any idea on how to confirm/reject this hypothesis?___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-07 Thread P.O. Jonsson 
Dear Erich,

> The roll back was done with a simple svn merge -c -11900,-11899 .
> So I'd assume it to be correct .. can you please specify which change you 
> think was rolled back incorrectly?
> 

I have tried this out on CentOS and the reason I see 5.0.0-1 instead of 
5.0.0-12054 is that  lines were removed that took care of that.

Adding these lines back into CMakeLists.txt:

   set(CPACK_RPM_PACKAGE_VERSION ${ORX_VERSION})
   set(CPACK_RPM_PACKAGE_RELEASE ${CPACK_PACKAGE_RELEASE})
   set(CPACK_RPM_PACKAGE_LICENSE "CPL")
   set(CPACK_RPM_PACKAGE_URL "http://www.oorexx.org/; )
   set(CPACK_PACKAGE_CONTACT "sahana...@users.sf.net" 
)
   set(CPACK_RPM_PACKAGE_GROUP "Development/Languages")
   set(CPACK_RPM_PACKAGE_VENDOR "Rexx Language Association")
   set(CPACK_PACKAGING_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}")
# remove 'csh'-dependency as it doesn't seem to be required
#  set(CPACK_RPM_PACKAGE_REQUIRES "csh")
   set(CPACK_RPM_PACKAGE_SUMMARY "Open Object Rexx is an object-oriented 
scripting language.")

instead of these lines 

   set(CPACK_RPM_PACKAGE_LICENSE "CPL")
   set(CPACK_RPM_PACKAGE_URL "http://www.oorexx.org/ ")
   set(CPACK_PACKAGE_CONTACT "sahana...@users.sf.net 
")
   set(CPACK_PACKAGING_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}")
# remove 'csh'-dependency as it doesn't seem to be required
#  set(CPACK_RPM_PACKAGE_REQUIRES "csh“)


Will solve the problem of a defunct version number reported for the package on 
CentOs.


The thing with not being able to revert to an older version of ooRexx is a 
murkier business. I do not think it is related to this change, I just had not 
noticed since I always build a newer version.

When building a specific revision (any revision) from a fresh SVN copy and 
thereafter installing using the resulting rpm everything is fine. BUT if I 
thereafter uninstall it (dnf remove) and try another previously built version 
rexx -v still give me the previous version (the one I just deinstalled). So 
there seems to be some kind of cashing going on that I cannot control. This may 
be CentOS related. 


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Changes in rev 12051

2020-04-07 Thread P.O. Jonsson 

> Am 07.04.2020 um 15:47 schrieb Erich Steinböck :
> 
> I think some changes introduced at a later stage was mistakenly removed by 
> that rollback
> Should not some of these settings be restored?
> The roll back was done with a simple svn merge -c -11900,-11899 .
> So I'd assume it to be correct .. can you please specify which change you 
> think was rolled back incorrectly?


There is a multitude of instructions for Cpack that I think are missing, hence 
the question. Compare before - after below.

This is what I see after installing a package built on CentOS (rpm build)
[osboxes@osboxes workspace]$ dnf list ooRexx
CentOS-8 - AppStream
6.2 MB/s | 6.6 MB 00:01
CentOS-8 - Base 
7.5 MB/s | 5.0 MB 00:00
CentOS-8 - Extras   
 16 kB/s | 4.9 kB 00:00
Installed Packages
ooRexx.x86_64 5.0.0-1   
   @@commandline
[osboxes@osboxes workspace]$ 

Before 12051 I think you could see 5.0.0-12050 etc. The  bigger problem is that 
when I uninstall (dnf remove) version 12051 or newer and install (def install 
or using the software install) it reports to have install for instance version 
12038 but a rexx -v reports 12054. Thus my conclusion that some of the lines 
below are really necessary.

I will try to add this to a local copy of CMakeLists.txt on Fedora and see if 
this solves the problem but not being able to go back is really worrying.

> 
> Also (but a minor point) should the license not be "CPLv1.0.txt“ ?
> The license is called CPL 1.0.  The change from CPACK_RPM_PACKAGE_LICENSE 
> "CPL 1.0" to .. "CPL" was made in response to an issue reported by you a few 
> months ago.
> 
> On Tue, Apr 7, 2020 at 10:32 AM P.O. Jonsson  > wrote:
> I have compared CMakeLists.txt from before and after the rollback. I think 
> some changes introduced at a later stage was mistakenly removed by that 
> rollback
> 
> In this section aroundset(CPACK_RPM_PACKAGE_LICENSE "CPL“) I found 
> differences:
> 
> Before rollback
> 
>set(CPACK_RPM_PACKAGE_VERSION ${ORX_VERSION})
>set(CPACK_RPM_PACKAGE_RELEASE ${CPACK_PACKAGE_RELEASE})
>set(CPACK_RPM_PACKAGE_LICENSE "CPL")
>set(CPACK_RPM_PACKAGE_URL "http://www.oorexx.org/ 
> ")
>set(CPACK_PACKAGE_CONTACT "sahana...@users.sf.net 
> ")
>set(CPACK_RPM_PACKAGE_GROUP "Development/Languages")
>set(CPACK_RPM_PACKAGE_VENDOR "Rexx Language Association")
>set(CPACK_PACKAGING_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}")
> # remove 'csh'-dependency as it doesn't seem to be required
> #  set(CPACK_RPM_PACKAGE_REQUIRES "csh")
>set(CPACK_RPM_PACKAGE_REQUIRES "hicolor-icon-theme")
> 
>set(CPACK_RPM_FILE_NAME ${CPACK_PACKAGE_FILE_NAME}.rpm)
>set(CPACK_RPM_PACKAGE_SUMMARY
> "Open Object Rexx is an object-oriented scripting language.")
> 
>
> configure_file(${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/oorexx.spec.in 
>  
> ${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/oorexx.spec)
>set(CPACK_RPM_USER_BINARY_SPECFILE 
> "${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/oorexx.spec")
> #   
> configure_file(${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_post.in 
>  
> ${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_post)
> #   set(CPACK_RPM_POST_INSTALL_SCRIPT_FILE 
> "${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_post")
> #   
> configure_file(${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_postun.in 
>  
> ${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_postun)
> #   set(CPACK_RPM_POST_UNINSTALL_SCRIPT_FILE 
> "${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_postun")
> 
> after rollback
> 
>set(CPACK_RPM_PACKAGE_LICENSE "CPL")
>set(CPACK_RPM_PACKAGE_URL "http://www.oorexx.org/ 
> ")
>set(CPACK_PACKAGE_CONTACT "sahana...@users.sf.net 
> ")
>set(CPACK_PACKAGING_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}")
> # remove 'csh'-dependency as it doesn't seem to be required
> #  set(CPACK_RPM_PACKAGE_REQUIRES "csh“)
> 
> 
> Should not some of these settings be restored?
> 
> Also (but a minor point) should the license not be "CPLv1.0.txt“ ?
> 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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
>

Re: [Oorexx-devel] Changes in rev 12051

2020-04-07 Thread Erich Steinböck 
>
> I think some changes introduced at a later stage was mistakenly removed by
> that rollback
> Should not some of these settings be restored?
>
The roll back was done with a simple svn merge -c -11900,-11899 .
So I'd assume it to be correct .. can you please specify which change you
think was rolled back incorrectly?

Also (but a minor point) should the license not be "CPLv1.0.txt“ ?
>
The license is called CPL 1.0.  The change from CPACK_RPM_PACKAGE_LICENSE
"CPL 1.0" to .. "CPL" was made in response to an issue reported by you a
few months ago.

On Tue, Apr 7, 2020 at 10:32 AM P.O. Jonsson  wrote:

> I have compared CMakeLists.txt from before and after the rollback. I think
> some changes introduced at a later stage was mistakenly removed by that
> rollback
>
> In this section aroundset(CPACK_RPM_PACKAGE_LICENSE "CPL“) I found
> differences:
>
> Before rollback
>
>set(CPACK_RPM_PACKAGE_VERSION ${ORX_VERSION})
>set(CPACK_RPM_PACKAGE_RELEASE ${CPACK_PACKAGE_RELEASE})
>set(CPACK_RPM_PACKAGE_LICENSE "CPL")
>set(CPACK_RPM_PACKAGE_URL "http://www.oorexx.org/;)
>set(CPACK_PACKAGE_CONTACT "sahana...@users.sf.net")
>set(CPACK_RPM_PACKAGE_GROUP "Development/Languages")
>set(CPACK_RPM_PACKAGE_VENDOR "Rexx Language Association")
>set(CPACK_PACKAGING_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}")
> # remove 'csh'-dependency as it doesn't seem to be required
> #  set(CPACK_RPM_PACKAGE_REQUIRES "csh")
>set(CPACK_RPM_PACKAGE_REQUIRES "hicolor-icon-theme")
>
>set(CPACK_RPM_FILE_NAME ${CPACK_PACKAGE_FILE_NAME}.rpm)
>set(CPACK_RPM_PACKAGE_SUMMARY
> "Open Object Rexx is an object-oriented scripting language.")
>
>configure_file(${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/
> oorexx.spec.in
> ${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/oorexx.spec)
>set(CPACK_RPM_USER_BINARY_SPECFILE
> "${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/oorexx.spec")
> #   configure_file(${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/
> rpm_post.in ${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_post)
> #   set(CPACK_RPM_POST_INSTALL_SCRIPT_FILE
> "${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_post")
> #   configure_file(${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/
> rpm_postun.in ${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_postun)
> #   set(CPACK_RPM_POST_UNINSTALL_SCRIPT_FILE
> "${CMAKE_CURRENT_SOURCE_DIR}/${ORX_PLATFORM_DIR}/rpm_postun")
>
> after rollback
>
>set(CPACK_RPM_PACKAGE_LICENSE "CPL")
>set(CPACK_RPM_PACKAGE_URL "http://www.oorexx.org/;)
>set(CPACK_PACKAGE_CONTACT "sahana...@users.sf.net")
>set(CPACK_PACKAGING_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}")
> # remove 'csh'-dependency as it doesn't seem to be required
> #  set(CPACK_RPM_PACKAGE_REQUIRES "csh“)
>
>
> Should not some of these settings be restored?
>
> Also (but a minor point) should the license not be "CPLv1.0.txt“ ?
>
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> ___
> 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