X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78B81.F9EAEABA@onstor-exch02.onstor.net>; Mon, 30 Apr 2007 16:47:56 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: flash_install.sh - Don't do it...
Date: Mon, 30 Apr 2007 16:47:56 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0346A3E8@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0346A3E7@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: flash_install.sh - Don't do it...
Thread-Index: AceLgABoKfmQrDw2T/KOmOQHifQeOwAADfGgAABpLrA=
From: "John Rogers" <john.rogers@onstor.com>
To: "John Rogers" <john.rogers@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Ken Renshaw" <ken.renshaw@onstor.com>
Cc: "John Keiffer" <john.keiffer@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>,
	<dl-data-management>

Nevermind, I think I understand. You are saying build-trees is a bad
place because of some issue.

-----Original Message-----
From: John Rogers=20
Sent: Monday, April 30, 2007 4:43 PM
To: Andy Sharp; Ken Renshaw
Cc: John Keiffer; dl-QA; dl-data-management
Subject: RE: flash_install.sh - Don't do it...

I am not sure what you mean by build procedure. I'm not arguing to keep
any particular process. I'm just trying to understand what you are
proposing.

Generally QA folk don't run flash_install.sh unless their system has
failed an upgrade process, that uses system upgrade. flash_install uses
build_trees which should be a known good(or well at least known) source
of compiled code.

I think you might be blurring some workflows. What I think you are
suggesting is that to recover a system, we should compile the source
code and then get it onto a flash card somehow.

-----Original Message-----
From: Andy Sharp=20
Sent: Monday, April 30, 2007 4:34 PM
To: Ken Renshaw
Cc: John Keiffer; dl-QA; dl-data-management
Subject: Re: flash_install.sh - Don't do it...

This problem I thought was fixed in the referenced version, but I
confess I don't always grok the QA version nomenclature.

Suffice it to say that this problem is of a category that has happened
more than once since I started here, and really cries out for "fixin"
the build procedure.

The official build procedure should start with a blank directory, p4
sync the entire branch, and build *everything*, producing the release
candidate.  I've brought this up before, and was told about history and
other things, but I don't recall any of it, so let's hear now in print
if there are any objections to adopting this as our build procedure.
Otherwise I will just forget again and ask the same question three
months from now.

Cheers,

a

On Mon, 30 Apr 2007 16:02:00 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> This is known in teh sub14 builds, sub15 due out tomorrow will have
> those defects addressed.
>=20
> Thanks,
>=20
> -Ken
>=20
>=20
> -----Original Message-----
> From: John Keiffer
> Sent: Mon 4/30/2007 3:54 PM
> To: dl-QA
> Cc: Andy Sharp
> Subject: flash_install.sh - Don't do it...
> =20
> FYI:
>=20
> =20
>=20
> After almost completely messing up my system for good, I decided to
