It should be clearly stated what is it for, because there are two different use scenario I see here:
1. User get somehow some software to try and install it in its own space. Like new compliler, or plugins etc and like to play with it without too much expectation on consistancy. 2. Group of user need their own software installation isolated from other users and mainainable within some sub-sysadmin within the group. For example group of developers working together on some project or group of finantianal analists working with Sas or somthing similar, group of AutoCAD desiners etc... So this software should be consistant, secured, mainainable etc. We should not sent misleading message with wrong names, which raise wrong expectations. So it will be fair to say that to substitute or make bit better user-level-installation, which now is tar-balls, we do small changes to pkgadd and patchadd to make user play with packages instead and give him some way to check dependancy some way tokeep consistancy. But we should clearly say that this is not for isolation, sharing and maintain software for work group and if you need more security and responcibility, more isolation - then zones will be perfectly suitable for this. And we are no recommending to use user-level-installation for such reasons. In short - yes let better call it User-Level-Installation not Software-Domain. Thanks, Vassili. This message posted from opensolaris.org
