Description of problem:

Transcript of sso mailing list discussion:

>>>>> There are two solutions. If a user is going to be administering IPA they
>>>>> might add /usr/sbin to their path. As a developer I always
>>>>> have /usr/sbin in my path because I frequently perform administration
>>>>> tasks.
>>>>>
>>>>> However that being said, I think one could argue many of the IPA command
>>>>> line tools might not constitute traditional UNIX administration
>>>>> utilities and are more akin to commands belonging to an application,
>>>>> which normally reside in /usr/bin. Thus the second option is to move the
>>>>> commands from /usr/sbin to /usr/bin, perhaps we should consider this.
>>>>
>>>> Yes, we should probably move most of them in /usr/bin
>>>> Luckily on Fedora they will start putting /usr/sbin in the default path
finally, but on RHEL it will matter for some time.
>>>>
>>>> Simo.
>>
>> I put them into /usr/sbin because these are definitely sys admin commands,
even if they don't necessarily happen while the user is 'root' or update the
local system.
>>
>> I'm flexible.
>>
>> This would happen post-beta but would be relatively trivial to fix in the
tree for new installs. Upgrades are slightly more complex.
>
> rpm takes care of that, unless you are thinking of make install kind of
upgrades :)
>

No, I was thinking rpm. We'll need a %pre or %post to remove the old bits
though, right? Or will that happen automagically? It would be nice if it did. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: