On Jul 4, 2009, at 8:43 AM, Milan Jurik <Milan.Jurik at Sun.COM> wrote:
> Hi James, > > James Carlson p??e v p? 03. 07. 2009 v 12:46 -0400: >> On Jul 2, 2009, at 9:28 PM, Roland Mainz <roland.mainz at nrubsig.org> >> wrote: >> >>> James Carlson wrote: >>>> Cedric Blancher writes: >>>>> On 21/06/2009, David.Comay at sun.com <David.Comay at sun.com> wrote: >>>>>> Sorry for missing this the first time but what is the >>>>>> justification for >>>>>> moving any utilities into SUNWcsu? SUNWcsu needs to be broken up >>>>>> into >>>>>> separate packages and not have additional content added into it. >>>>> >>>>> I believe putting the fundamental POSIX commands into a package >>>>> which >>>>> is always installed is the right thing. Otherwise you break >>>>> scripts >>>>> without reason. >>>> >>>> There's no difference between SUNWesu and SUNWcsu from that >>>> perspective. Both are in the SUNWCmreq metacluster, meaning that >>>> they're installed on all Solaris systems and cannot be de- >>>> selected in >>>> any supported manner. >>> >>> Ok... but why was the "SUNesu" package originally be created ? >> >> Fair question, but as I no longer have access to Sun's internal data, >> I couldn't tell you. At a guess, it was from an earlier attempt at >> organizing the delivered software. It's also possible that it >> reflects a Sun internal organization issue; different groups work >> independently. >> > > I am not sure if Sun internal data can give you more info, PSARC case > from 1991 is not very talkative about the package content. But from > package names - SUNWesu was not considered as part of the core > cluster, > the deliverables from SUNWesu were not so important. I'm not sure what you're referring to, but SUNWesu has been a part of SUNWCmreq for as long as I can recall.
