OpenDS Integration into OpenSolaris [ LSARC/2008/691 FastTrack timeout 11/19/2008]
Gilles Bellaton
Gilles.Bellaton at Sun.COM
Tue Nov 18 08:36:33 PST 2008
Putting executables in /usr/bin and /usr/lib add some complexity and
requires to rename many executables.
Since those executables are already shipped and used by opends users
this either create compatibility
would it be acceptable to simply put everything under /usr/opends and
ask administrator to run
the commands from /usr/opends/bin ?
Gilles
> Tom Childers wrote:
>> Everyone,
>>
>> The timer on this case expires on Wednesday. Going through this
>> discussion, I want to confirm two recommended changes, and resolve a
>> naming headache they create:
>>
>> 1. Move the OpenDS componentry from /opt to /usr, consistent with
>> OpenLDAP and other FOSS products.
>>
>> 2. Update the documentation to recommend installation under user and
>> group "ldap", instead of "opends".
>>
>> (1) needs clarification. If we follow the OpenLDAP example, then we
>> will be putting executables in /usr/bin and /usr/lib/opends. This
>> will cause problems in /usr/bin, since they have executables called
>> backup
>> status
>> manage-tasks
>
> Either put them in /usr/lib/opends/bin/
>
> Or prefix them with opends.
>
> Or make an opends command and put just that in /usr/bin and all the
> real commands are in /usr/lib/opends/bin/ but appear as subcommands of
> opends.
>
>> etc. Should the project team propose new names for the
>> executables? (OpenLDAP prefixes all their executables with "oldap".)
>
> Acutally the prefix is openldap not oldap because the later can be
> confused as meaning "old ap"
>
>
More information about the opensolaris-arc
mailing list