No issue here. Ray
Ray Weber
admin@xxxxxxxx
413-784-3870
________________________________
From: ldm-users <ldm-users-bounces@xxxxxxxxxxxxxxxx> on behalf of Pete Pokrandt
via ldm-users <ldm-users@xxxxxxxxxxxxxxxx>
Sent: Wednesday, November 9, 2022 12:09:44 AM
To: Steven Emmerson <emmerson@xxxxxxxx>; LDM <ldm-users@xxxxxxxxxxxxxxxx>
Subject: Re: [ldm-users] Contemplated change to LDM installation procedure
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Works for me!
Pete
Pete Pokrandt - System Engineer IV
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx
________________________________
From: ldm-users <ldm-users-bounces@xxxxxxxxxxxxxxxx> on behalf of Steven
Emmerson <emmerson@xxxxxxxx>
Sent: Tuesday, November 8, 2022 4:41 PM
To: LDM <ldm-users@xxxxxxxxxxxxxxxx>
Subject: [ldm-users] Contemplated change to LDM installation procedure
Hi,
We're contemplating a change to the installation procedure for the LDM and
would like to know if and how this will affect you. Currently, if the option
"--disable-root-actions" isn't specified, the configure(1)-script will test to
see if the user has root privileges. We're thinking of abandoning this in favor
of a more simplified installation process in which the user would first build
and install the LDM as themself and then the superuser (i.e., root) would
execute the command "make root-actions". This last step could be done by the
same user via su(1) or sudo(1) or later by a systems administrator.
This change would allow the use of GitHub's actions for continuous integration
testing (why it would is a long story) and is something which is greatly
desired.
Please let us know if this would negatively affect your LDM installation
practice in an unacceptable way by posting to this mailing-list.
Regards,
Steve Emmerson
Stonie Cooper
