replication of stuff in /usr/gnu

[Richard L. Hamilton]

[...]
> We aren't going to be able to provide packaging
>  boundaries for all
> possible combinations of binaries.  Finding a useful
>  set of boundaries
> that allow us to reach some commonly held target
>  installations would
>  be an achievable engineering goal.

At first, I was going to say that for those needing to minimize,
" 'removef' is your friend".  But then the problem becomes what
happens when Sun packages start containing scripts that depend
on the peculiarities of individual GNU utilities?  Minimizing below
package level looks like it can't be easily done, since dependencies
are only at the package level.  OTOH, more smaller packages increases
overhead on distro media and slows installation and updating.

Consistency _and_ flexibility is difficult...


> > I've recently been through the pain of trying to
> get a Solaris system to 
> > fit within 2GB.  It couldn't be easily done,
> without a lot of time 
> > figuring out what I could safely remove, and what I
> couldn't, without 
> > impacting the system's usability as a host for
> running the NIC driver 
> > test suites.  (I didn't need graphics, etc.)  I
> spent time manually 
> > trying to identify cases, in some cases 200k at a
> time!  So I'm 
> > particularly sensitive here.
> 
> Having that list would be helpful in various
>  discussions, I expect.
> Certainly Glynn and David have been probing
>  equivalent choices in the
> Indiana discussion (as, I presume, have the Nexenta
>  team in their
>  forum).
>   - Stephen

Yeah, one of the possible benefits of a variety of distros and even
packaging approaches is that there's a wider range _and_ depth of
experience to explore and feed back into refinements of what may
arguably be the prototypical distro(s).
 
 
This message posted from opensolaris.org