James Falkner wrote:
> Right now users can install arbitrary software in $HOME and it will
> be unknown to the admin. What this proposal suggests is using a
> subset of the Solaris packaging technology to allow and encourage
> the use of packaging tools to install into $HOME - potentially giving
> the admin a better interface to discover installed stuff across the
> users' home directories on a given system, rather than no interface
> today, while still allowing non-root use of existing package
> technology (which is the main goal of this proposal). The proposal
> is not meant to boil the ocean, but rather take a baby step toward
> a more friendly non-root environment for developers and app
> administrators.
>
What I want to do is not boil the ocean (that project seems
to be proceeding apace, anyway), but define where we're headed.
Given these two requests:
1) installation and patching of multiple instances of the same packages
in different locations
2) use of the packaging tools by non-root users
what would a "boiled ocean" version look like?
I want to understand where we're headed, not what set of
(incomplete) modifications will address your project's
current requirements.
- Bart
--
Bart Smaalders Solaris Kernel Performance
barts at cyber.eng.sun.com http://blogs.sun.com/barts
