Eric Boutilier <[EMAIL PROTECTED]> wrote:
> This wish caught my eye because several people mentioned it here.
>
> The thing is the Companion CD package maintainers did provide some
> build information. So to help out in this regard, I just grabbed it all
> and put it in a central location.
>
> Wha
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 n
On Wednesday 24 August 2005 04:09 am, ken mays wrote:
> Alan & Others,
>
> Yes, the sources are available for the Companion CD
> as posted on the website and can be put on a DVD as
> well for those that would like to rebuild the code.
> Yet, I think historically a few things were missing -
> the no
On Wed, 24 Aug 2005, ken mays wrote:
>
>
> --- Eric Boutilier <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 24 Aug 2005, Joerg Schilling wrote:
> > > Alan DuBoff <[EMAIL PROTECTED]> wrote:
> > >
> > > > [...]
> > > > The source packages have always been available
> > for the Companion CD, just that
> >
--- Eric Boutilier <[EMAIL PROTECTED]> wrote:
> On Wed, 24 Aug 2005, Joerg Schilling wrote:
> > Alan DuBoff <[EMAIL PROTECTED]> wrote:
> >
> > > [...]
> > > The source packages have always been available
> for the Companion CD, just that
> > > they grew so large that they were not included
> on
On Wed, 24 Aug 2005, Eric Boutilier wrote:
> What I'm talking about are the special README files (called sfw.README)...
Correction: This should have said README.sfw not sfw.README.
Eric
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolari
On Wed, 24 Aug 2005, Joerg Schilling wrote:
> Alan DuBoff <[EMAIL PROTECTED]> wrote:
>
> > [...]
> > 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
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
Hey,
> Also, what about a Year 2005 experience of getting not
> only the original source but the fully patched and
> modified source that can be downloaded and rebuilt
> with just a simple './configure' instead of having to
> search and add several patches (this is not only in
> open source but in
--- 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 use
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
Hey,
On Wed, 2005-08-24 at 11:37 +0200, 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 l
Shawn Walker <[EMAIL PROTECTED]> wrote:
> I don't see what a companion CD that ships with a commercial version
> of Solaris has to do with OpenSolaris. I also think you're being
> rather unnecessarily negative. It seems to me that this is a business
> related decision, not a community one...
If S
|> > I'd word this slightly differently: there is merit in being given the
|> > choice during OS install of "do you want to install freeware as well?".
|> > Where exactly this freeware comes from, especially for non-Sun
|> > distributions, may be up for debate.
|>
|> +1. It'd be great for the OS in
On Tue, 23 Aug 2005, Hugh McIntyre wrote:
>
> |> Nevertheless, I think the Companion CD concept still has merit. There
> |> are lots of customers who have a strong desire for any unsupported
> |> open-source software they might use to come from the same vendor that
> |> they purchased their platfor
|> Nevertheless, I think the Companion CD concept still has merit. There
|> are lots of customers who have a strong desire for any unsupported
|> open-source software they might use to come from the same vendor that
|> they purchased their platform/service contract from.
I'd word this slightly di
Because there are countless people outside Sun with expertise in
building and maintaining open-source software, enabling a way for
non-Sun people to contribute to the Companion CD probably should have
happened _a long_ time ago. Nevertheless, I think the Companion CD
concept still has merit. There
James Dickens wrote:
this isn't about grunt work, its about who controls the gate, and sun
endorsing this person and his project above the rest of the others.
This sounds more like a "glossary cache miss" than evidence of a conspiracy.
The role of a gatekeeper is very different in the FOSS an
On 8/23/05, Alan Coopersmith <[EMAIL PROTECTED]> wrote:
> Matt Ingenthron wrote:
> > It occurs to me that the term "gatekeeper" is really more from Sun's
> > teamware source control legacy and could carry a negative connotation to
> > someone in the community who is not (or only loosely) familiar w
Hi James,
James Dickens wrote:
(snip...)
>
>
>As long as its numbers are being padded by downloads that are on the
>main solaris 10 download page, it will appear to be alive. I did a
>quick poll in #solaris and #opensolaris, and got 2 responders that
>say they actually use the freeware compani
sorry meant this to be on the list as well...
On 8/23/05, Stephen Lau <[EMAIL PROTECTED]> wrote:
> James Dickens wrote:
> > On 8/23/05, Stephen Lau <[EMAIL PROTECTED]> wrote:
> >
> >>James Dickens wrote:
> >>
> >>>sorry this is opensolaris, and not the ON distrobution, sun doesn't
> >>>have the r
Matt Ingenthron wrote:
It occurs to me that the term "gatekeeper" is really more from Sun's
teamware source control legacy and could carry a negative connotation to
someone in the community who is not (or only loosely) familiar with the
term.
I've never worked in a consolidation with a formal
Hi James,
Stephen Lau wrote:
James Dickens wrote:
sorry this is opensolaris, and not the ON distrobution, sun doesn't
have the right to pick the "gate keeper" of a community without a
discussion on the subjec and possibly a vote, this seems very
underhanded. I value sun choices f
James Dickens wrote:
sorry this is opensolaris, and not the ON distrobution, sun doesn't
have the right to pick the "gate keeper" of a community without a
discussion on the subjec and possibly a vote, this seems very
underhanded. I value sun choices for my OS, but I have found sun's
choices for
On 8/23/05, James Dickens <[EMAIL PROTECTED]> wrote:
> sorry this is opensolaris, and not the ON distrobution, sun doesn't
> have the right to pick the "gate keeper" of a community without a
> discussion on the subjec and possibly a vote, this seems very
> underhanded. I value sun choices for my O
On 8/17/05, Marilyn Shoemaker <[EMAIL PROTECTED]> wrote:
> We plan to push development for the Solaris Companion out into the community,
> to serve as a test case for community development for other areas of Solaris.
> The Companion is the supplemental collection of open source software
> distri
Marilyn Shoemaker wrote:
We plan to push development for the Solaris Companion out into the community,
Why the Companion?
... It's supplemental to Solaris and consequently not subject to reviews by
internal architecture committees,
Ummm,
While the end result may be the same (no
On Thu, 18 Aug 2005, Steven Christensen wrote:
>
> It may be a little early to create a community, but not too early to
> start defining the problems we need to solve and what a community
> might do...
Regarding defining problems we need to solve, scope is probably
something that should be discuss
Glynn -
It may be a little early to create a community, but not too early to
start defining the problems we need to solve and what a community
might do. What I would like to see immediately here is a good summary
of
1. What are our packaging goals?
2. What systems are available and what are the
On Thu, 18 Aug 2005, Glynn Foster wrote:
> Hey,
>
> > First, my thanks to Dennis for his very kind and supportive comments.
> > I have always enjoyed, and will continue to enjoy, working with him
> > and the members of Blastwave. I fully expect to have our individual
> > communites join together w
On 8/17/05, Steven Christensen <[EMAIL PROTECTED]> wrote:
> First, my thanks to Dennis for his very kind and supportive comments.
> I have always enjoyed, and will continue to enjoy, working with him
> and the members of Blastwave. I fully expect to have our individual
> communites join together w
Heya,
> The packages from the companion cd, or blastave or sunfreeware will all be
> regular solaris packages. I guess that Steve as gatekeeper will be
> responsible for building the actual packages, so the community effort will
> be mainly around the source.
>
> However a packaging community
Hi,
Glynn Foster wrote:
Any thoughts for creating a packaging community, or is it too early to
go that direction just yet?
Not a bad idea.
The packages from the companion cd, or blastave or sunfreeware will all be
regular solaris packages. I guess that Steve as gatekeeper will be
responsibl
On Wed, 17 Aug 2005, Dennis Clarke wrote:
> On 8/17/05, Rich Teer <[EMAIL PROTECTED]> wrote:
> > On Thu, 18 Aug 2005, Ian Collins wrote:
> >
> > > True, but is duplication?
>
> I am entirely happy with the decision by Sun management to bring in
> Steve Christensen as the project lead on this. He
Hey,
> First, my thanks to Dennis for his very kind and supportive comments.
> I have always enjoyed, and will continue to enjoy, working with him
> and the members of Blastwave. I fully expect to have our individual
> communites join together with the OpenSolaris world of develpers to
> define
First, my thanks to Dennis for his very kind and supportive comments.
I have always enjoyed, and will continue to enjoy, working with him
and the members of Blastwave. I fully expect to have our individual
communites join together with the OpenSolaris world of develpers to
define and deploy the l
On Thu, Aug 18, 2005 at 10:05:11AM +1200, Ian Collins wrote:
> True, but is duplication?
Possibly, which is why I'd like to see this community-packaged
software effort grow to include everyone. Whether that will be
possible depends on how well we can accomodate varied interests in one
place.
>
On 8/17/05, Rich Teer <[EMAIL PROTECTED]> wrote:
> On Thu, 18 Aug 2005, Ian Collins wrote:
>
> > True, but is duplication?
I am entirely happy with the decision by Sun management to bring in
Steve Christensen as the project lead on this. He has been working
with Solaris and the open source softw
On Thu, 18 Aug 2005, Ian Collins wrote:
> True, but is duplication?
Not necessarily, but choice usually implies some sort of duplication
of effort.
> Remember these are the same applications, so why duplicate the porting
> effort? It would be better to build a Solaris 8 and up and Solaris 10
>
Rich Teer wrote:
On Thu, 18 Aug 2005, Ian Collins wrote:
Isn't this a duplication of effort, we already have Blastwave. Or is
this seen as somehow complimentary?
I see them as complimentary. For example, Blastwave's packages are
supported on S8+, whereas the Companion CD presumably
On Thu, 18 Aug 2005, Ian Collins wrote:
> Isn't this a duplication of effort, we already have Blastwave. Or is
> this seen as somehow complimentary?
I see them as complimentary. For example, Blastwave's packages are
supported on S8+, whereas the Companion CD presumably doesn't have
that restric
Marilyn Shoemaker wrote:
We plan to push development for the Solaris Companion out into the community, to serve as a test case for community development for other areas of Solaris. The Companion is the supplemental collection of open source software distributed with Solaris.
Isn't this a
We plan to push development for the Solaris Companion out into the community,
to serve as a test case for community development for other areas of Solaris.
The Companion is the supplemental collection of open source software
distributed with Solaris.
The source code repository, the gate, w
43 matches
Mail list logo