X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C79E2F.840FD194@onstor-exch02.onstor.net>; Thu, 24 May 2007 11:15:31 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C79E2F.840FD194"
References: <20070523175727.11cd43d2@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D15C@onstor-exch02.onstor.net><20070524093353.0571d0d4@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D164@onstor-exch02.onstor.net> <20070524110606.3039767e@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: need to build 1.3.3 latest
Date: Thu, 24 May 2007 11:15:31 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D172@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: need to build 1.3.3 latest
Thread-Index: AceeLjMt9cSJs2yERTmhvKxJX8+WsQAAJtBJ
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C79E2F.840FD194
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Correct, in light of recent events all branches are complete in this =
regard, i.e. are completely self-contained. 1.3.3 is the last codeline =
where the BSD was revved separately from EverON, so the pain only =
applies to this one situation. Sorry it had to be you. FWLIW almost =
noone ever builds out of the rel branches since they are mainly for me =
to assemble patches in, and you could have actually used R1_3_3_work, a =
complete branch for dev work, at the 1.3.3.0 cutoff point and not had =
these issues.

Somewhere back in prehistoric times this all made sense...I'll just be =
glad when it's all relegated to folklore.


-----Original Message-----
From: Andy Sharp
Sent: Thu 5/24/2007 11:06 AM
To: Ken Renshaw
Subject: Re: need to build 1.3.3 latest
=20
Would it be out of line to say this is broken?  If those files are
needed, they should be in the branch under perforce.  How does
walnut-brain (me) know what files to get and from where?  I might even
go so far as to say the symlink should also be in perforce if the
openbsd tree isn't in the branch.  I guess it's not what I'm used to,
but AFAIK this process isn't documented anywhere.  Of course, this is
1.3.3 so we wouldn't be fixing anything there, but I'm guessing that
in light of events we have changed this methodology for current and
future branches, si?

Cheers,

a

On Thu, 24 May 2007 09:56:32 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> Without seeing the error, you probably need these files at the same
> level as nfx-tree:
>=20
> Copy these four files from /n/Build-Trees/R1.3.3.0/pieces
>=20
> gdb
> descr
> descr-bc
> Makefile
>=20
> Setup this symlink:
>=20
> openbsd.new -> /usr/openbsd.new ( which in turn points
> to /n/Build-Trees/BSD/openbsd-latest-133 )
>=20
> When you're done you should have a directoty that looks like this:
>=20
> nfx-tree
> openbsd.new
> gdb
> descr
> descr-bc
> Makefile
>=20
> Sorry about the hoops, this is from before when I'd only branch
> nfx-tree and reuse the openbsd and other components. All 2.x and 3.x
> branches are complete branches, i.e. with openbsd and the straggler
> files.
>=20
> If make release still fails, let me know what the errors are or send
> me the login info and location on your machine and I'll check it out.
>=20
> -Ken
>=20
>=20
>=20
> -----Original Message-----
> From: Andy Sharp
> Sent: Thu 5/24/2007 9:33 AM
> To: Ken Renshaw
> Subject: Re: need to build 1.3.3 latest
> =20
> I tried that, but "make release" in R1_3_3_X_rel/nfx-tree doesn't
> work.
>=20
> On Wed, 23 May 2007 18:28:20 -0700 "Ken Renshaw"
> <ken.renshaw@onstor.com> wrote:
>=20
> > Hey Andy. If you want the latest 1.3.3.x patched release, 1.3.3.17 I
> > think, then you need to use this nfx-tree view:=20
> > //depot/R1_3_3_X_rel/nfx-tree/...@24002 ( current top of tree )
> > =20
> > If you want the 1.3.3.0 GA release use this view:
> > =20
> > //depot/R1_3_3_X_rel/nfx-tree/...@21707
> > =20
> > If you want to use the canned openbsd for this release, just set:
> > =20
> > /usr/openbsd.new -> /n/Build-Trees/BSD/openbsd-latest-133
> > =20
> > Let me know if you need to know anything else Andy.
> > =20
> > -Ken
> >=20
> > ________________________________
> >=20
> > From: Andy Sharp
> > Sent: Wed 5/23/2007 5:57 PM
> > To: Ken Renshaw
> > Subject: need to build 1.3.3 latest
> >=20
> >=20
> >=20
> > Hi Ken,
> >=20
> > I need to build the latest 1.3.3 code, but I don't seem know where
> > that is.  I found a branch called R1_3_3_work, but the nfx-tree code
> > does not build in that tree.  I can't find any other likely place to
> > look. Can you tell me where the official branch is for the latest
> > 1.3.3?
> >=20
> > Thanks,
> >=20
> > a
> >=20
> >=20
>=20


------_=_NextPart_001_01C79E2F.840FD194
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: need to build 1.3.3 latest</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Correct, in light of recent events all branches are =
complete in this regard, i.e. are completely self-contained. 1.3.3 is =
the last codeline where the BSD was revved separately from EverON, so =
the pain only applies to this one situation. Sorry it had to be you. =
FWLIW almost noone ever builds out of the rel branches since they are =
mainly for me to assemble patches in, and you could have actually used =
R1_3_3_work, a complete branch for dev work, at the 1.3.3.0 cutoff point =
and not had these issues.<BR>
<BR>
Somewhere back in prehistoric times this all made sense...I'll just be =
glad when it's all relegated to folklore.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Thu 5/24/2007 11:06 AM<BR>
To: Ken Renshaw<BR>
Subject: Re: need to build 1.3.3 latest<BR>
<BR>
Would it be out of line to say this is broken?&nbsp; If those files =
are<BR>
needed, they should be in the branch under perforce.&nbsp; How does<BR>
walnut-brain (me) know what files to get and from where?&nbsp; I might =
even<BR>
go so far as to say the symlink should also be in perforce if the<BR>
openbsd tree isn't in the branch.&nbsp; I guess it's not what I'm used =
to,<BR>
but AFAIK this process isn't documented anywhere.&nbsp; Of course, this =
is<BR>
1.3.3 so we wouldn't be fixing anything there, but I'm guessing that<BR>
in light of events we have changed this methodology for current and<BR>
future branches, si?<BR>
<BR>
Cheers,<BR>
<BR>
a<BR>
<BR>
On Thu, 24 May 2007 09:56:32 -0700 &quot;Ken Renshaw&quot;<BR>
&lt;ken.renshaw@onstor.com&gt; wrote:<BR>
<BR>
&gt; Without seeing the error, you probably need these files at the =
same<BR>
&gt; level as nfx-tree:<BR>
&gt;<BR>
&gt; Copy these four files from /n/Build-Trees/R1.3.3.0/pieces<BR>
&gt;<BR>
&gt; gdb<BR>
&gt; descr<BR>
&gt; descr-bc<BR>
&gt; Makefile<BR>
&gt;<BR>
&gt; Setup this symlink:<BR>
&gt;<BR>
&gt; openbsd.new -&gt; /usr/openbsd.new ( which in turn points<BR>
&gt; to /n/Build-Trees/BSD/openbsd-latest-133 )<BR>
&gt;<BR>
&gt; When you're done you should have a directoty that looks like =
this:<BR>
&gt;<BR>
&gt; nfx-tree<BR>
&gt; openbsd.new<BR>
&gt; gdb<BR>
&gt; descr<BR>
&gt; descr-bc<BR>
&gt; Makefile<BR>
&gt;<BR>
&gt; Sorry about the hoops, this is from before when I'd only branch<BR>
&gt; nfx-tree and reuse the openbsd and other components. All 2.x and =
3.x<BR>
&gt; branches are complete branches, i.e. with openbsd and the =
straggler<BR>
&gt; files.<BR>
&gt;<BR>
&gt; If make release still fails, let me know what the errors are or =
send<BR>
&gt; me the login info and location on your machine and I'll check it =
out.<BR>
&gt;<BR>
&gt; -Ken<BR>
&gt;<BR>
&gt;<BR>
&gt;<BR>
&gt; -----Original Message-----<BR>
&gt; From: Andy Sharp<BR>
&gt; Sent: Thu 5/24/2007 9:33 AM<BR>
&gt; To: Ken Renshaw<BR>
&gt; Subject: Re: need to build 1.3.3 latest<BR>
&gt;&nbsp;<BR>
&gt; I tried that, but &quot;make release&quot; in R1_3_3_X_rel/nfx-tree =
doesn't<BR>
&gt; work.<BR>
&gt;<BR>
&gt; On Wed, 23 May 2007 18:28:20 -0700 &quot;Ken Renshaw&quot;<BR>
&gt; &lt;ken.renshaw@onstor.com&gt; wrote:<BR>
&gt;<BR>
&gt; &gt; Hey Andy. If you want the latest 1.3.3.x patched release, =
1.3.3.17 I<BR>
&gt; &gt; think, then you need to use this nfx-tree view:<BR>
&gt; &gt; //depot/R1_3_3_X_rel/nfx-tree/...@24002 ( current top of tree =
)<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt; If you want the 1.3.3.0 GA release use this view:<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt; //depot/R1_3_3_X_rel/nfx-tree/...@21707<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt; If you want to use the canned openbsd for this release, just =
set:<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt; /usr/openbsd.new -&gt; =
/n/Build-Trees/BSD/openbsd-latest-133<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt; Let me know if you need to know anything else Andy.<BR>
&gt; &gt;&nbsp;<BR>
&gt; &gt; -Ken<BR>
&gt; &gt;<BR>
&gt; &gt; ________________________________<BR>
&gt; &gt;<BR>
&gt; &gt; From: Andy Sharp<BR>
&gt; &gt; Sent: Wed 5/23/2007 5:57 PM<BR>
&gt; &gt; To: Ken Renshaw<BR>
&gt; &gt; Subject: need to build 1.3.3 latest<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt; &gt; Hi Ken,<BR>
&gt; &gt;<BR>
&gt; &gt; I need to build the latest 1.3.3 code, but I don't seem know =
where<BR>
&gt; &gt; that is.&nbsp; I found a branch called R1_3_3_work, but the =
nfx-tree code<BR>
&gt; &gt; does not build in that tree.&nbsp; I can't find any other =
likely place to<BR>
&gt; &gt; look. Can you tell me where the official branch is for the =
latest<BR>
&gt; &gt; 1.3.3?<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks,<BR>
&gt; &gt;<BR>
&gt; &gt; a<BR>
&gt; &gt;<BR>
&gt; &gt;<BR>
&gt;<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C79E2F.840FD194--
