AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070524131859.02f130f8@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<ken.renshaw@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E02F3D172@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 24 May 2007 13:20:05 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>
Subject: Re: need to build 1.3.3 latest
Message-ID: <20070524132005.10db3989@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D172@onstor-exch02.onstor.net>
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>
	<BB375AF679D4A34E9CA8DFA650E2B04E02F3D172@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 24 May 2007 11:15:31 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> 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.

Is there a tagging convention or something for the "cutoff point"?  I
did try to build in R1_3_3_work but there is a compilation error in
nfx-tree so that made me think I was in the wrong place.

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

Yeah well all this stuff is basically ancient history now, so I'm just
going to la-la-la while covering my eyes and pretend none of it ever
happened.

> -----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
>  
> 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:
> > 
> > Copy these four files from /n/Build-Trees/R1.3.3.0/pieces
> > 
> > gdb
> > descr
> > descr-bc
> > Makefile
> > 
> > Setup this symlink:
> > 
> > openbsd.new -> /usr/openbsd.new ( which in turn points
> > to /n/Build-Trees/BSD/openbsd-latest-133 )
> > 
> > When you're done you should have a directoty that looks like this:
> > 
> > nfx-tree
> > openbsd.new
> > gdb
> > descr
> > descr-bc
> > Makefile
> > 
> > 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.
> > 
> > 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.
> > 
> > -Ken
> > 
> > 
> > 
> > -----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
> >  
> > I tried that, but "make release" in R1_3_3_X_rel/nfx-tree doesn't
> > work.
> > 
> > On Wed, 23 May 2007 18:28:20 -0700 "Ken Renshaw"
> > <ken.renshaw@onstor.com> wrote:
> > 
> > > 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: 
> > > //depot/R1_3_3_X_rel/nfx-tree/...@24002 ( current top of tree )
> > >  
> > > If you want the 1.3.3.0 GA release use this view:
> > >  
> > > //depot/R1_3_3_X_rel/nfx-tree/...@21707
> > >  
> > > If you want to use the canned openbsd for this release, just set:
> > >  
> > > /usr/openbsd.new -> /n/Build-Trees/BSD/openbsd-latest-133
> > >  
> > > Let me know if you need to know anything else Andy.
> > >  
> > > -Ken
> > > 
> > > ________________________________
> > > 
> > > From: Andy Sharp
> > > Sent: Wed 5/23/2007 5:57 PM
> > > To: Ken Renshaw
> > > Subject: need to build 1.3.3 latest
> > > 
> > > 
> > > 
> > > Hi Ken,
> > > 
> > > 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?
> > > 
> > > Thanks,
> > > 
> > > a
> > > 
> > > 
> > 
> 
