On Wednesday 24 August 2005 06:21 am, Joerg Schilling wrote: > Alan DuBoff <[EMAIL PROTECTED]> wrote: > > On Wednesday 24 August 2005 02:37 am, Joerg Schilling wrote: > > > I should note that things in the OSS community do not start by talking > > > about them but by doing something. Why is there no place to look at the > > > whole source tree that is used by Sun to create /opt/sfw packages? > > > People don't like to buy a cat in a bag, they like to see whether it > > > makes sense to work on the current /opt/sfw build system or whether it > > > makes more sense to start from scratch or with a new idea like > > > Blastwave. > > > > The source packages have always been available for the Companion CD, just > > that they grew so large that they were not included on the CD, AFAIK. You > > can download them from http://www.sun.com/software/solaris/freeware/ at > > your convenience. > > I know this, but it is a different thing to sometimes have a prosa text > that explains what has been done from having the build environment. > > It would also help to be able to load things in a simpler way that does not > count against the life time of the mouse buttons.... > > Let me make an example that comes into my mind because I recently did > receive a list of mkisofs problems from Sun: > > If Sun compiles mkisofs the wrong way (not large file aware) and does not > dosument this, how does it help if people may load the unmodified sources > from http://www.sun.com/software/solaris/freeware/?
I don't think anyone is intentionally obfuscating things from the community, just that this is "work in progress" for the most part. The OpenSolaris team (Marilyn specific) is now responsible for the Companion CD, AFAIK, so let's let them see how they can make things better for folks like you in the community. -- Alan DuBoff - Sun Microsystems Solaris x86 Engineering _______________________________________________ opensolaris-discuss mailing list [email protected]
