> Hi guys, in some thread I read that Indiana is experiment, so, as I
> understand, even when you release stable version, it will not stable. For my
> opinion it's not true way.
I think that Ian Murdock has already said that it is not an experiment and
that it will be used as the next rendidtion of the SXDE. It is a Sun
product and it has the OpenSolaris TradeMark on it which Sun Microsystems
Inc owns and controls.
So think of it as a future looking Solaris OS type product.
> Also, why you name packages with prefix SUNW? Most peoples look for gcc, for
> example, but can't find it. May be more user-frendly name packages as most
> of us expect?
Because SUNW was the old Sun Microsystems Stock symbol I guess. Also
because every package in the Sun Solaris product inventory that goes into
Solaris has a name of SUNWfoo for some foo. This means that the dependency
tree for SUNWfoo may include SUNWbar which may also have a dependency on
SUNWwoo. Therefore no one wanted to reinvent the where and thus all the
packages in a Project Indiana or OpenSolaris Binary product release will
have packages named SUNWfoo and SUNWbar and SUNWwoo. That is my guess.
> And last one, why you can't merge you efforts with guys from Nexenta and
> blastware and make one big repository?
That would imply that the community driven software release would have
community driven software resources for it and that makes sense. It seems
obvious.
One common complaint about Blastwave is that it duplicates a lot of things
in Solaris and OpenSolaris. That is true. It is also quite wrong. It is
wrong in that we *should* have a community facility and process by which the
community cna contribute up to date software titles into OpenSolaris, going
forwards and long term.
Over the last few days I worked around the clock with Angelo Rajadurai to
get as much software into an IPS style repo for people to use. The process
is flawed and it tends to break easily. We don't know why. We can install
packages from the repo to an Indiana user. Sometimes. There is no facility
for post install or pre-install scripts and we may have to just create our
own solution to address that.
Let me give you an example.
First .. look at the software list at :
http://blastwave.network.com:10000/
The page is wrong and I don't know why. There should be 1600 packages there
but it only reports 25.
If you download and install the OpenSolaris(tm) Binary Release you can do
this to get GCC 4.0.2 :
export PKG_IMAGE=/
export PKG_SERVER=http://blastwave.network.com:10000
export PATH=/opt/csw/bin:/usr/xpg4/bin:/usr/sbin:/usr/bin
Get a full package list thus :
pkg image-create -F -a blastwave=http://blastwave.network.com:10000 /
pkg refresh
pkg status -va
Install GCC 4.0.2 thus :
# pkg install IPSgcc4core
DOWNLOAD PKGS FILES XFER (MB)
Completed 2/2 127/127 25.87/25.87
PHASE ACTIONS
Install Phase 193/193
There is no post-install script facility within IPS so you have to run the
mkheaders script yourself .. for now :
# cd /opt/csw/gcc4/bin
# ./mkheaders
Then check to make sure you have a good GCC 4.0.2 :
# /opt/csw/gcc4/bin/gcc -v
Reading specs from /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.0.2/specs
Target: i386-pc-solaris2.8
Configured with: ../sources/gcc-4.0.2/configure --prefix=/opt/csw/gcc4
--with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
--enable-shared --enable-multilib --enable-nls --with-included-gettext
--with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib
--with-system-zlib --enable-languages=c,c++,f95,java,objc,ada
Thread model: posix
gcc version 4.0.2
You can do the same thing with GCC 3.4.5 if you want but I used our (
Blastwave ) GCC 4.0.2 to build and backport the SUNWipkg software that is
running on both Sparc and AMD64 and it works just fine on Solaris 10. Well,
that is to say it does what it does. Not fine but okay for now. It is a
moving picture and we are getting there. As a community ?
If you try to install bzip2 you will have no problems :
-bash-3.2# pkg refresh
-bash-3.2# pkg install IPSbzip2
DOWNLOAD PKGS FILES XFER (MB)
Completed 1/1 32/32 1.68/1.68
PHASE ACTIONS
Install Phase 50/50
-bash-3.2# /opt/csw/bin/bzip2 --version
bzip2, a block-sorting file compressor. Version 1.0.3, 15-Feb-2005.
Copyright (C) 1996-2005 by Julian Seward.
This program is free software; you can redistribute it and/or modify
it under the terms set out in the LICENSE file, which is included
in the bzip2-1.0 source distribution.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
LICENSE file for more details.
bzip2: I won't write compressed data to a terminal.
bzip2: For help, type: `bzip2 --help'.
You can install GCC 3.4.5 also :
-bash-3.2# pkg install IPSgcc3
DOWNLOAD PKGS FILES XFER (MB)
Completed 9/9 531/531 89.68/89.68
PHASE ACTIONS
Install Phase 930/930
Then go run the mkheaders script manually :
-bash-3.2# cd /opt/csw/gcc3/bin
-bash-3.2# ./mkheaders
Then look at it :
-bash-3.2# /opt/csw/gcc3/bin/gcc -v
Reading specs from /opt/csw/gcc3/lib/gcc/i386-pc-solaris2.8/3.4.5/specs
Configured with: ../sources/gcc-3.4.5/configure --prefix=/opt/csw/gcc3
--with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
--enable-shared --enable-multilib --enable-nls --with-included-gettext
--with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib
--enable-languages=all
Thread model: posix
gcc version 3.4.5
If you try to install something trivial like gzip the process fails and I
don't know why yet. In fact, there is no promise that anything from there
works as expected ( yet ) because pre and post install scripts don't work in
the IPS world and the SVR4 package standard, which we all used for at least
a decade, needed those. Also, I do not know if we can take advantage of
isaexec in order to select the best binary from a range of options after
install. That would be one reason that gzip fails to install because it uses
isaexec to select the arch target binary. There are many other problems.
[this part will sting a bit]
Lastly, all of this software exists and is built by the community for the
community on both x86 and on Sparc. Yes, all of this will be available for
Sparc too. It always has been. Heck, it already does. It has been built by
software maintainers that wanted to help themselves as well as help their
fellow Solaris user. Over the past five years I have invested a ton of my
own dollars into keeping everything running. Certainly back in the days when
bandwidth was $2500 a month on a saturated T1 line. Those were tough days.
When I sold my house ( and my last Corvette ) in 2003 I made sure Blastwave
kept running. It has always been a dead loss. Most people ( 99.97% ) in Sun
have no clue about that because they are busy playing politics and flaunting
job titles that mean *nothing*. So they are primarily lost wandering
children the moment you stop their pay check. Just ask Mr Martin marTux
Bochnig [1] about the real world and he will tell you.
[back to statements of fact]
So yes, Blastwave drags in a whack of stuff that duplicates what is already
in the newer Solaris/OpenSolaris revs but in most cases the community driven
software creation and distribution process at Blastwave engages people from
all walks of life and from all over the world. The process has always been
about "one Solaris user helping another Solaris user" and we have worked
very hard to ensure that we are consistent.
Not perfect.
We the community, desperately, right now, need to put the breath of life
back into OpenSolaris.org and then to work together. We need to stop this
insanity of working behind closed doors and running riot in many directions.
We need to work together.
If we were to smooth out some things, some relationship concerns, and then
work in a common direction then we would have an OS release called
OpenSolaris(tm) which has a vast deep and wide software tree available to
it. Up to date. Maintained and delivered from the community to the
community.
* We would have the OpenSolaris user helping the next OpenSolaris user. *
This has *always* been my vision and I never walked away from it.
Dennis Clarke
Founder and SysAdmin
Blastwave.org
[1] http://www.flickr.com/photos/stiefkind/409011208/
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
