Darren Reed wrote: > Rich Burridge wrote: >> ... >> 3. Business Summary >> >> 3.1. Problem Area: >> >> Perl is a very commonly-used tool, and is used to deliver Solaris >> functionality (kstat(1M), projadd(1M), projdel(1m) etc.), it is >> used by >> the Apache we ship with Solaris and it is used by several >> unbundled >> tools (e.g. SunCluster) > > In other words, after this project integrates, parts of an install of ON > will > not work without parts of SFW also being installed. Is a circular > dependency > like that desired?
It already exists and has done so for years. A consolidation is not the install boundary. Install boundaries are collections of packages which may come from multiple consolidations. > Is it acceptable for someone to to a build and install of only ON and have > documented programs that do not function because the interpreter is > missing? > Is that impossible or just something we don't care about? It isn't possible nor is it actually expected. > To me it seems like perl is a core part of the system and thus should be > in ON... So are other things already in SFW. Such as libxml2 (needed by SMF), Python (needed by the new pkg system). The legacy package tools come from a different consolidation as do other critical packages such as SUNWtls. At a rough count I found at least 4 consolidations involved in the SUNWCmreq install cluster - which is the one smaller than the SUNWCrnet that is visible during interactive installed. SUNWCmreq is the bare minimum that the legacy Nevada and Solaris 10 installers will let you install. -- Darren J Moffat
