This bug is created as a clone of upstream ticket:
Now that https://fedorahosted.org/389/ticket/528 is fixed, the next step is to allow building the server with the instance specific scripts disabled.
Add a new configure option:
AC_ARG_ENABLE(instance-scripts, AS_HELP_STRING([--enable-instance-scripts], [Enable setup to create instance specific scripts in the system lib/dirsrv directory (default: yes)])
The default is yes, so as not to break any existing builds. If you do not want setup to create the instance specific scripts, use configure ... --disable-instance-scripts
Per email discussion, changing this to RFE.
Fix Description: Instead of defining a configure option, we provide a new
option in setup-ds.pl, slapd.InstScriptsEnabled?, which defaults to false. All
new installs of 389 will NOT install with a inst_dir nor the scripts that are in
Additionally, this change fixes setup-ds.pl to correctly use the sbindir scripts
to start/stop the server instance during installation.
Finally, we add support for setup-ds.pl so that in --update if the inst_dir
exists, scripts will be updated, but if it does not exist, no action is taken.
In time, we will alter --update to *remove* the scripts within inst_dir during
the update (We have no way of knowing if a customer has put custom scripts in
Doc bug: https://bugzilla.redhat.com/show_bug.cgi?id=1324907
And by default old behaviour will be kept, i.e. scripts will be installed.
A minor bug - https://bugzilla.redhat.com/show_bug.cgi?id=1348903
Rest worked as expected.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.