On Monday 24 April 2006 09:59 am, Eric Boutilier wrote:
another impressive (heavily used and proven) build environment is
the Sun GNOME (JDS) ports system based on pkgbuild.
Don't forget about pkgsrc either, AFAIK, they're off happily building packages
as well.
--
Alan DuBoff - Sun
Eric Boutilier [EMAIL PROTECTED] wrote:
And when it finds that certain /usr/sfw or more tightly integrated
bits need to be updated, this can be driven from the CCD community
directly...
+1.
An up-to-date CCD (and JDS) drives an up-to-date SFW, which reduces
(dramatically reduces?) the
ken mays [EMAIL PROTECTED] wrote:
3. What is being done currently with colleges,
universities, and organizations?? Isn't NetBSD doing
work in providing packages/ports to Solaris using the
NetBSD build system?!?
As long as build systems that are coming from other OS
add patches that are not
Joerg Schilling wrote:
Robert Milkowski [EMAIL PROTECTED] wrote:
I myself would prefer open source software based on libraries already
included in Solaris (like OpenSSL) - something I can't get with
Blastwave.
This is something that currently does not fit the ON OSS model from Sun.
Joerg Schilling wrote:
As long as build systems that are coming from other OS
add patches that are not needed or counter-productive on
our OS, it does not help much.
Yeah, you hit the nail on the head when it comes to pkgsrc. In my work
with pkgsrc, I found this to be maybe the biggest
ken mays wrote:
So far, three systems have come to pass which are
impressive for auto porting code to Solaris:
1. Portaris (Gentoo's Portage for Solaris)
2. Nexenta's Autobuilder
3. Blastwave's SVN/builder (maintained by Cory)
There are the others done by NetBSD, OpenPKG, and many
other
(moving to companion-discuss)
On Wednesday 19 April 2006 08:35 am, Eric Boutilier wrote:
I'm not sure Nexenta's implementation is the way to go though. It seems
to me that Phil's pkg-get -- being designed around Sun's implementation
of the SVr4 packaging standard -- seems like the better
On Monday 17 April 2006 08:05 pm, Eric Boutilier wrote:
Hi Alan,
On Mon, 17 Apr 2006, Alan DuBoff wrote:
...
everyone, the blastwaves, the nexentras, pkgsrc, et
all...or is this even possible? I think it would be
possible to give these folks an option by having a
common set of
So far, three systems have come to pass which are
impressive for auto porting code to Solaris:
1. Portaris (Gentoo's Portage for Solaris)
2. Nexenta's Autobuilder
3. Blastwave's SVN/builder (maintained by Cory)
There are the others done by NetBSD, OpenPKG, and many
other people porting open
On Wednesday 19 April 2006 04:25 pm, Eric Boutilier wrote:
I'm not sure if that's what Alan is pushing for or not, but one things
for sure: It seems way more logical to speculate that a significant
percentage of volunteers in such an endeavor would be Sun employees as
well as non-Sun
[ sorry for the brutal snippage ]
Maybe this new bullpen project needs to be built on the CSW project,
maybe the CCD project, maybe the JDS (spec-files-extra) project, maybe
something else, maybe a hybrid...
In any case, I'm really looking forward to that being figured out ASAP.
I think
On Thursday 20 April 2006 05:38 am, Dennis Clarke wrote:
Let's drop the name Sun from that last sentence.
Try, just for the feel of it, to put in the words the community in
as a replacement for the company name Sun.
Now see how it feels :
I think I'm on the same page with you
Pffft... everyone here understands what is meant, and it's a lot easier
than trying to describe,
closer to 'one of those types of machines that is based around
what is commonly called a linux distribution, and/or
a Linux Standards Base compliant system in addition to adhering to
Philip Brown wrote:
On Mon, Apr 17, 2006 at 04:23:17PM -0700, Alan DuBoff wrote:
So, how would it be possible to build a large set of libraries that everyone
could update and use together? Is this at all possible? Sun has basically
proposed to work with the community, and that is
Philip Brown wrote:
On Tue, Apr 18, 2006 at 05:54:15PM -0500, Eric Boutilier wrote:
Philip Brown wrote:
The thing about all that, is that it forces the machine to be closer and
closer to a linux machine, until eventually, it becomes nothing more than a
linux machine with a
ken mays wrote:
There is the small piece of the pie in which the
community really needs the support of Sun engineers in
provide quality desktop environments and graphic
libraries comparable to competing server/desktop OSes.
Namely, KDE/GNOME support which is being done very
well by the
Eric Boutilier wrote:
ken mays wrote:
...
The other is having a tool like apt-get in which you
can install software from a CD/DVD archive set of from
a remote mirrored FTP site...
...
+1. (That can not be overemphasized if you ask me.)
I'll just point out, for those of you who haven't
Philip Brown wrote:
On Tue, Apr 18, 2006 at 06:10:31PM -0700, Alan DuBoff wrote:
Sun has staff now to handle most of what they do, but this doesn't
allow Sun to work with the community.
btw: there's a difference between working with the community, and
meeting the needs of the
On Mon, Apr 17, 2006 at 11:02:20PM -0700, Erast Benson wrote:
On Mon, 2006-04-17 at 22:08 -0700, ken mays wrote:
Going back to the comments about Nexenta build system:
Nexenta build system == Debian build system
The equation above means that NexentaOS following
Debian Policy[1] as close
On Tue, 2006-04-18 at 14:50 -0700, Philip Brown wrote:
On Mon, Apr 17, 2006 at 11:02:20PM -0700, Erast Benson wrote:
On Mon, 2006-04-17 at 22:08 -0700, ken mays wrote:
Going back to the comments about Nexenta build system:
Nexenta build system == Debian build system
The equation
On Tue, Apr 18, 2006 at 05:54:15PM -0500, Eric Boutilier wrote:
Philip Brown wrote:
The thing about all that, is that it forces the machine to be closer and
closer to a linux machine, until eventually, it becomes nothing more than a
linux machine with a user-invisible solaris kernel.
On Tue, 2006-04-18 at 16:14 -0700, Philip Brown wrote:
On Tue, Apr 18, 2006 at 05:54:15PM -0500, Eric Boutilier wrote:
Philip Brown wrote:
The thing about all that, is that it forces the machine to be closer and
closer to a linux machine, until eventually, it becomes nothing more than a
Casper Dik wrote:
I know Solaris has a slower release cycle - but with CCD developed by
Open Solaris community it could change - I mean CCD could be uptodate
as Blastwave or other projects. Now it would be up to client if he/she
wants the latest from OpenSolaris or Solaris release boundled CCD.
On Mon, 17 Apr 2006, Eric Boutilier wrote:
An up-to-date CCD (and JDS) drives an up-to-date SFW, which reduces
(dramatically reduces?) the need for distros and ports projects to install
duplicate libraries.
Or put another way, the OpenSolaris standard base improves in a way that
Hi,
On Thu, 2006-04-13 at 14:52 -0500, Eric Boutilier wrote:
Another +1 here.
And for another huge reason why it's important to go hash it out ASAP,
consider the build systems that the other distros are planning/doing for
freeware apps:
- The SchilliX project plans to implement the
On Tue, 2006-04-18 at 13:26 +1200, Glynn Foster wrote:
Hi,
On Thu, 2006-04-13 at 14:52 -0500, Eric Boutilier wrote:
Another +1 here.
And for another huge reason why it's important to go hash it out ASAP,
consider the build systems that the other distros are planning/doing for
Hi Alan,
On Mon, 17 Apr 2006, Alan DuBoff wrote:
...
everyone, the blastwaves, the nexentras, pkgsrc, et
all...or is this even possible? I think it would be
possible to give these folks an option by having a
common set of libs that Sun and Community participates
in, what do you think?
We
Going back to the comments about Nexenta build system:
1. What ever happened to running Debian/Linux packages
natively (or by wrapper)??
2. Can we build from Nexenta in providing Debian
packages for Schillix, SXCR, and Belenix???
3. What is being done currently with colleges,
universities, and
Dennis Clarke wrote:
... I am still bothered by what appears to be a desire on the
part of Sun to reproduce all of this except inside Sun and
for the purposes of being Sun blessed...
This is an assertion already made by you and already proven
completely groundless -- especially the inside
++casper, or another +1.
Where I work, it is difficult to get open source from somewhere other than the
CCD. Unless it is bundled with Solaris, it is somehow seen as less official
and has to go through multiple hoops. If this dicussion leads to the CCD as
simply being a snapshot of
Stephen Potter wrote:
++casper, or another +1.
Another +1 here.
And for another huge reason why it's important to go hash it out ASAP,
consider the build systems that the other distros are planning/doing for
freeware apps:
- The SchilliX project plans to implement the SchilliX build
Eric Boutilier wrote:
Stephen Potter wrote:
++casper, or another +1.
Another +1 here.
And for another huge reason why it's important to go hash it out ASAP,
consider the build systems that the other distros are planning/doing for
freeware apps:
- The SchilliX project plans to
I think a better idea might be to create something like Blastwave but for
Solaris 10 Sparc and x86, where we can just install software into /opt/sfw
using pkg-get or something similar. It'll be far more useful than a
co-bundled product, which gets too stale to be useful over time.
see :
33 matches
Mail list logo
