--- Alan DuBoff <[EMAIL PROTECTED]> wrote:
> On Wednesday 13 July 2005 07:57, Keith M Wesolowski
> wrote:
> > On Wed, Jul 13, 2005 at 07:49:59AM -0700, Alan
> Coopersmith wrote:
> > > The problem with that is since the Companion CD
> is only updated with new
> > > Solaris releases, you'ld be stuck with whatever
> the latest version on a
> >
> > That can be changed. I wasn't sure we were really
> ready for this
> > discussion, but since we're having it anyway,
> don't consider anything
> > sacred. If changing the way the companion CD were
> developed and
> > released could bring all the dependency stacks
> together, it can be
> > done.
>
> That would only work if other parties were in
> agreement to link against them,
> and providing they could be updated quick enough.
>
> --
>
> Alan DuBoff - Sun Microsystems
> Solaris x86 Engineering - Sun on Sun is the way of
> the future!
Mainly, it as to do with availability of
libraries/headers on Solaris at the level of the
current Debian or Gentoo distributions. Also, a
regulated update cycle. See, the Companion CD hasn't
been updated in quite some time with many of the
libraries **AND** headers needed for advanced
development work. So many of the maintainers and
developers have to 'spin' their own library builds.
We have SunFreeware (SFW) and Blastwave (CSW). The
majority of Solaris developers will use those
distributions if not using just the Companion CD
(SFW). Many of the Sun admins use /usr/sfw because it
has been around for years and use by the Companion CD.
Yet, the reality is that it is hard to lock down ONE
directory for all development libraries and headers.
Why? Because when you closely look at Blastwave'
standards, you'll see it is more of a development
structure by nature. I don't speak for Dennis, but
after dealing with Blastwave for quite some time...I
see that is has grown into more of an application
development environment. Sunfreeware has many tools
and libraries, but Blastwave resembles a bit more in
regards to a large 'distribution' of Solaris software
on ar to Linux/*BSD distributors. So this results in a
higher need of certain libraries and headers being
updated consistently (i.e. GNOME/KDE) where
Sunfreeware may not need that many updates or there
could be a corporate QA structured policy that Sun has
to follow before releasing packages or making requests
for packages.
I bring this up because it is not so simple to just
toss everything into one development directory and
call it a day (although we could if everyone wanted
it!). We have to organize how things will be
maintained and supported over time (just like the
other distributors). So when I want the latest copy of
GIMP or libxml2 on the Companion CD or openSolaris
Software Community website, I make a request and it
gets done by the maintainer within a designated
timeframe. ;o>
This will make building KDE a lot easier than having a
separate 100+ MB requirement package of libraries and
other stuff and we can use that same package to build
GNOME 2.10.2.
Just thoughts...
Ken Mays @ EarthLink, Inc.
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
_______________________________________________
opensolaris-discuss mailing list
[email protected]
