Re: [osol-discuss] b137 based on tonic or otherwise
On Sat, Apr 17, 2010 at 2:38 AM, Jürgen Keil jrgn.k...@googlemail.comwrote:
I don't know why but I
expected that the release build to be available in
the Mercurial repository after it gets released.
$ hg clone -r b111b ssh://anon at hg dot opensolaris dot
org/hg/onnv/onnv-gate
abort: unknown revision 'b111b'!
So no, you cannot build previous releases of the OpenSolaris
distribution making it a closed product.
It's not in the mercurial repository, but there is:
http://dlc.sun.com/osol/on/downloads/b111b/
http://dlc.sun.com/osol/on/downloads/
So it's probably what someone mentioned on another mailing list, that it was
difficult to keep that branch/respin in the main repository because of some
incompatibility/limitation in the old SCM. And they didn't expose it but it
was archived somewhere.
I knew I was missing something, thanks for clearing that out. We probably
will see a b134{a,b,c} directory in the future (or even in the repository).
--
Giovanni
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On Wed, Apr 14, 2010 at 2:22 PM, Giovanni Tirloni gtirl...@sysdroid.comwrote:
As some Oracle employees have already pointed out, that distribution is
*their* product. If that's the true spirit of things, it would make sense
why commits are not public and they probably see integrating the b134{a,b,c}
code into the public repository as a contribution to the OpenSolaris
project.
Sorry for answering myself here.
I don't know why but I expected that the release build to be available in
the Mercurial repository after it gets released.
$ hg clone -r b111b ssh://a...@hg.opensolaris.org/hg/onnv/onnv-gate
abort: unknown revision 'b111b'!
So no, you cannot build previous releases of the OpenSolaris distribution
making it a closed product. How can one expect it to be a reference binary
distribution ? I expected reference to mean something you can build on.
IMHO, a complete fork might not be the best option due to all the
engineering effort required but contributing to a distribution that's not
the official OpenSolaris binary distribution from Oracle/Sun is well within
the resources of the community.
Please someone correct me if I'm wrong about the source code availability of
build 111b. I'm probably missing something.
As I've often stated, it's all a matter of figuring where one wants to be
and adjusting expectations. It's just hard to figure it out sometimes so
there are a lot of missed expectations.
--
Giovanni
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
Hello,
Something is brewing:
http://dlc.sun.com/osol/on/downloads/b138/
~ Ken
--- On Fri, 4/16/10, Giovanni Tirloni gtirl...@sysdroid.com wrote:
From: Giovanni Tirloni gtirl...@sysdroid.com
Subject: Re: [osol-discuss] b137 based on tonic or otherwise
To: Dennis Clarke dcla...@blastwave.org
Cc: opensolaris-discuss@opensolaris.org
Date: Friday, April 16, 2010, 4:16 PM
On Wed, Apr 14, 2010 at 2:22 PM, Giovanni Tirloni gtirl...@sysdroid.com wrote:
As some Oracle employees have already pointed out, that distribution is *their*
product. If that's the true spirit of things, it would make sense why commits
are not public and they probably see integrating the b134{a,b,c} code into the
public repository as a contribution to the OpenSolaris project.
Sorry for answering myself here.
I don't know why but I expected that the release build to be available in the
Mercurial repository after it gets released.
$ hg clone -r b111b ssh://a...@hg.opensolaris.org/hg/onnv/onnv-gate
abort: unknown revision 'b111b'!
So
no, you cannot build previous releases of the OpenSolaris
distribution making it a closed product. How can one expect it to be a
reference binary distribution ? I expected reference to mean something you
can build on.
IMHO, a complete fork might
not be the best option due to all the engineering effort required but
contributing to a distribution that's not the official OpenSolaris
binary distribution from Oracle/Sun is well within the resources of the
community.
Please someone correct me if I'm wrong about the source code availability of
build 111b. I'm probably missing something.
As I've often stated, it's all a matter of figuring where one wants to be and
adjusting expectations. It's just hard to figure it out sometimes so there are
a lot of missed expectations.
--
Giovanni
-Inline Attachment Follows-
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On Fri, Apr 16, 2010 at 5:31 PM, ken mays maybird1...@yahoo.com wrote: Hello, Something is brewing: http://dlc.sun.com/osol/on/downloads/b138/ That's good news but it doesn't answer the hard questions in my two previous emails. It's like throwing a bone. -- Giovanni ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On Fri, Apr 16, 2010 at 11:31 PM, ken mays maybird1...@yahoo.com wrote: Hello, Something is brewing: http://dlc.sun.com/osol/on/downloads/b138/ I wouldn't take it as a sign of something exceptional - nothing new here. There are also b135, b136, b137 as well as almost any previous build. This side of the operation continues to tick-tock as always... -- Regards, Cyril ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
I don't know why but I expected that the release build to be available in the Mercurial repository after it gets released. $ hg clone -r b111b ssh://anon at hg dot opensolaris dot org/hg/onnv/onnv-gate abort: unknown revision 'b111b'! So no, you cannot build previous releases of the OpenSolaris distribution making it a closed product. It's not in the mercurial repository, but there is: http://dlc.sun.com/osol/on/downloads/b111b/ http://dlc.sun.com/osol/on/downloads/ -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On Wed, Apr 14, 2010 at 11:37 AM, Dennis Clarke dcla...@blastwave.orgwrote: On 04-14-10, Paul Gress pgr...@optonline.net wrote: I don't think he wants to start a new distro, he's looking to publishb137. That's about it in a nutshell. I have no shortage of build servers and thus I was thinking, if this is really open source ( with redistributables ) then a person with a bit of experience *should* be able to compile everything from the ground up and have a distro-looking-thing that anyone anywhere can download and run. Really, Jörg is better at this than I. I'm really a pretty simple guy, people need or want something, I'm sitting on top of a bucket load of servers and mirror sites. Gee, make coffee and do something. Not much more complex than that. I'm not getting political or anything subversive. I'm just trying to solve a problem in the community. Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Hey Dennis, That was the only way to 'get' opensolaris anyway .. build/bfu it. I still do from time to time. There is of course: http://dlc.sun.com/osol/docs/content/dev/DistroConst/using.html Good to see you 'round again Dennis. -- Cheers, Steven --- Steven Acres Toronto OpenSolaris User Group TOROSUG Leader http://opensolaris.org/os/project/torosug ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On Wed, Apr 14, 2010 at 12:37 PM, Dennis Clarke dcla...@blastwave.orgwrote:
On 04-14-10, Paul Gress pgr...@optonline.net wrote:
I don't think he wants to start a new distro, he's looking to
publishb137.
That's about it in a nutshell. I have no shortage of build servers and thus
I was thinking, if this is really open source ( with redistributables ) then
a person with a bit of experience *should* be able to compile everything
from the ground up and have a distro-looking-thing that anyone anywhere can
download and run. Really, Jörg is better at this than I.
I'm really a pretty simple guy, people need or want something, I'm sitting
on top of a bucket load of servers and mirror sites. Gee, make coffee and do
something. Not much more complex than that. I'm not getting political or
anything subversive. I'm just trying to solve a problem in the community.
Unless you're committing code through the sponsor program (!!), some people
think you're not contributing anything.
If we're looking forward to release 2010.$who_knows ourselves in its current
state, I think it's better to use the actual source code from where it's
going to be built by Oracle.
AFAIK, the next release was branched from b134 but it includes backports
from the other development builds that superseded it. It's probably called
b134a, b134b or something like that, right ?
The genunix website doesn't show any additional tags for b134* (
http://hg.genunix.org/onnv-gate.hg/tags). That repository is a mirror from
the actual internal repository where the developers commit their work.
$ hg clone ssh://a...@hg.opensolaris.org/hg/onnv/onnv-gate onnv-b134
requesting all changes
adding changesets
adding manifests
adding file changes
added 12161 changesets with 142449 changes to 58360 files
updating to branch default
42546 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg update -r onnv_134
7388 files updated, 0 files merged, 1270 files removed, 0 files unresolved
$ hg update -r onnv_134a
abort: unknown revision 'onnv_134a'!
$ hg update -r onnv_134b
abort: unknown revision 'onnv_134b'!
$ hg update -r onnv_134c
abort: unknown revision 'onnv_134c'!
Does anyone know how to get the source code that is going to be the next
release ?
As some Oracle employees have already pointed out, that distribution is
*their* product. If that's the true spirit of things, it would make sense
why commits are not public and they probably see integrating the b134{a,b,c}
code into the public repository as a contribution to the OpenSolaris
project.
Not exactly how things work in other (successful) open source projects.
--
Giovanni
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
While we're at it... I am running b134 and use the dev branch; when 2010.new
comes out, how do I switch and stick with that until we get further along
towards the 2010.Fall ( assuming these release issues get resolved)?
On Wed, Apr 14, 2010 at 10:22 AM, Giovanni Tirloni gtirl...@sysdroid.comwrote:
On Wed, Apr 14, 2010 at 12:37 PM, Dennis Clarke dcla...@blastwave.orgwrote:
On 04-14-10, Paul Gress pgr...@optonline.net wrote:
I don't think he wants to start a new distro, he's looking to
publishb137.
That's about it in a nutshell. I have no shortage of build servers and
thus I was thinking, if this is really open source ( with redistributables )
then a person with a bit of experience *should* be able to compile
everything from the ground up and have a distro-looking-thing that anyone
anywhere can download and run. Really, Jörg is better at this than I.
I'm really a pretty simple guy, people need or want something, I'm sitting
on top of a bucket load of servers and mirror sites. Gee, make coffee and do
something. Not much more complex than that. I'm not getting political or
anything subversive. I'm just trying to solve a problem in the community.
Unless you're committing code through the sponsor program (!!), some people
think you're not contributing anything.
If we're looking forward to release 2010.$who_knows ourselves in its
current state, I think it's better to use the actual source code from where
it's going to be built by Oracle.
AFAIK, the next release was branched from b134 but it includes backports
from the other development builds that superseded it. It's probably called
b134a, b134b or something like that, right ?
The genunix website doesn't show any additional tags for b134* (
http://hg.genunix.org/onnv-gate.hg/tags). That repository is a mirror from
the actual internal repository where the developers commit their work.
$ hg clone ssh://a...@hg.opensolaris.org/hg/onnv/onnv-gate onnv-b134
requesting all changes
adding changesets
adding manifests
adding file changes
added 12161 changesets with 142449 changes to 58360 files
updating to branch default
42546 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg update -r onnv_134
7388 files updated, 0 files merged, 1270 files removed, 0 files unresolved
$ hg update -r onnv_134a
abort: unknown revision 'onnv_134a'!
$ hg update -r onnv_134b
abort: unknown revision 'onnv_134b'!
$ hg update -r onnv_134c
abort: unknown revision 'onnv_134c'!
Does anyone know how to get the source code that is going to be the next
release ?
As some Oracle employees have already pointed out, that distribution is
*their* product. If that's the true spirit of things, it would make sense
why commits are not public and they probably see integrating the b134{a,b,c}
code into the public repository as a contribution to the OpenSolaris
project.
Not exactly how things work in other (successful) open source projects.
--
Giovanni
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
--
David
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On 04/14/10 01:33 PM, David E. Anderson wrote: While we're at it... I am running b134 and use the dev branch; when 2010.new comes out, how do I switch and stick with that until we get further along towards the 2010.Fall ( assuming these release issues get resolved)? Just set your client to use the '/release' repository for the 'opensolaris.org' publisher, and be certain you don't image-update using the '/dev' repository before then: pfexec pkg set-publisher \ -O http://pkg.opensolaris.org/release opensolaris.org Cheers, -Shawn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On 04/14/10 03:17 PM, Shawn Walker wrote: On 04/14/10 01:33 PM, David E. Anderson wrote: While we're at it... I am running b134 and use the dev branch; when 2010.new comes out, how do I switch and stick with that until we get further along towards the 2010.Fall ( assuming these release issues get resolved)? Just set your client to use the '/release' repository for the 'opensolaris.org' publisher, and be certain you don't image-update using the '/dev' repository before then: pfexec pkg set-publisher \ -O http://pkg.opensolaris.org/release opensolaris.org Basically 2010.04 will be b134a or b134b, which is still upgrading from b134. So it should work if you don't upgrade to =b135 dev prior to 2010.04. Paul ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b137 based on tonic or otherwise
On Wed, Apr 14, 2010 at 03:31:25PM -0400, Paul Gress wrote: Basically 2010.04 will be b134a or b134b, which is still upgrading from b134. So it should work if you don't upgrade to =b135 dev prior to 2010.04. And, right here, we have one of the best user-focused reasons for pausing the /dev repo at the pre-release base build while the release cycle is in progress. It may be frustrating, it may not suit some of us, but it is at least understandable. The only alternative is yet another repo with a different policy - not pausing for releases, and maybe with a quicker/automated test cycle as soon as a tag is laid down (or even nightly?). If the end result of these experiments in building from source is the establishment of such a repo, along with publication of what was learned along the way for others to use too, then it would be a great contribution to the community. -- Dan. pgppVDhzDFmS6.pgp Description: PGP signature ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
