| Date Of Receipt: 25-JAN-1996 14:07:19.22
From: SMURF::WASTED::"[email protected]"
To: [email protected]
CC: [email protected]
Subj: Re: Passing source through filter on checkin and checkout.
Yaacov, when you say "before the user gets it", do you mean the
"end customer" on an installed system?
The source that you bci/bsubmit is in the src pool, src files do not
ship to customers on the kit, but only files in the output tree (which
first get built in the obj tree).
Therefore, as part of getting the file into obj and output, you can,
in your Makefile, do whatever you want. If it's a matter of a sed
script, our makefiles are already setup for this; just identify the
files as DATAFILES and set SED_OPTIONS appropriately. If it's more
complicated, you may need to have your filter as a separate script
submitted into the source pool, which you execute using "sh ..." from
the Makefile.
For makefile help please mail to buildhelp if need assistance; there
are examples in the pool of customized makefiles which use specialized
filters or executables as part of the build process. Look for example
at the 'zic' or 'tic' code.
-josh
----------
From [email protected] Thu Jan 25 12:47:25 1996
Delivery-Date: Thu, 25 Jan 96 12:47:41 -0500
Date: Thu, 25 Jan 1996 12:47:49 -0500
From: [email protected] (Yaacov Fenster, Process Improvement, Quality and testing tools @ZKO3/4W15 381-1154)
To: [email protected]
Subject: Passing source through filter on checkin and checkout.
X-Vms-To: [email protected]
X-Vms-Cc: FENSTER
Is there a way to hook ode so that I can pass the checked in/out source code
through a filter after/before the user gets it ?
Thanx in advance
Yaacov
% -------------------------------------------------
% Yaacov Fenster (603)-881-1154 DTN 381-1154
% [email protected] [email protected]
% Policy 1: All phone calls are to be returned right away.
% Policy 2: All e-mail messages are to be responded to (and hopefully resolved)
% within 24 hours of reading.
% All the opinions voiced are mine alone and do not reflect anyone else's
% opinion. (Including my employer's).
|
| Date Of Receipt: 25-JAN-1996 14:57:57.72
From: SMURF::WASTED::"[email protected]" "Tom Tresvik"
To: "Yaacov Fenster, Process Improvement, Quality and testing tools @ZKO3/4W15 381-1154" <[email protected]>
CC: [email protected]
Subj: Re: Passing source through filter on checkin and checkout.
Yaacov,
While you may get a "yes" answer, I'm sure we'd like to know what you
intend to do inside sych a filter. If your improving the tools, then we
should consider such improvements for everyone. Remember we all use a
common tool set.
Tom
-----------------
Yaacov Fenster, Process Improvement, Quality and testing tools
@ZKO3/4W15 381-1154 wrote:
>
> Is there a way to hook ode so that I can pass the checked in/out source code
> through a filter after/before the user gets it ?
>
> Thanx in advance
>
> Yaacov
> % -------------------------------------------------
> % Yaacov Fenster (603)-881-1154 DTN 381-1154
> % [email protected] [email protected]
> % Policy 1: All phone calls are to be returned right away.
> % Policy 2: All e-mail messages are to be responded to (and hopefully resolved)
> % within 24 hours of reading.
> % All the opinions voiced are mine alone and do not reflect anyone else's
> % opinion. (Including my employer's).
|
| Date Of Receipt: 29-JAN-1996 10:49:20.90
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 29-Jan-1996 1046"
To: [email protected]
CC: jmf@DEC:.zko.flume, tresvik@DEC:.zko.flume, odehelp@DEC:.zko.flume
Subj: Re: Passing source through filter on checkin and checkout.
Yaacov, can you explain more about what you'd like to achieve; can you
provide an example? From the configuration management standpoint, I can't
see any reason why one would want the source code that is under the CM
system to be different than the source code as it presents itself when
the file's checked-out for edit, which is how I interpret your question:
> I mean the source code. Let's say that I want to check out file a.c.
> I want the ability to modify it in the process of being checked out and
> in the process of checking it back in. (Not neccessarily the same way)
Logically, this would mean that the file that is in the pool after the
check-in is not the same as was tested. Similarly, the file in the
user sandbox after a check-out is not the same as the file in the
product build.
I don't get what you're trying to do???
-josh
------- Forwarded Message
Date: Sun, 28 Jan 1996 19:49:39 -0500
Message-Id: <[email protected]>
From: [email protected] (Yaacov Fenster, Process Improvement, Quality
and testing tools @ZKO3/4W15 381-1154)
To: [email protected]
Subject: Resend: Re: Passing source through filter on checkin and checkout.
> From: SMTP%"[email protected]" 25-JAN-1996 14:07:34.76
> To: [email protected]
> CC: [email protected]
> Subj: Re: Passing source through filter on checkin and checkout.
>
> Yaacov, when you say "before the user gets it", do you mean the
> "end customer" on an installed system?
>
> The source that you bci/bsubmit is in the src pool, src files do not
> ship to customers on the kit, but only files in the output tree (which
> first get built in the obj tree).
I mean the source code. Let's say that I want to check out file a.c.
I want the ability to modify it in the process of being checked out and
in the process of checking it back in. (Not neccessarily the same way)
>
> Therefore, as part of getting the file into obj and output, you can,
> in your Makefile, do whatever you want. If it's a matter of a sed
> script, our makefiles are already setup for this; just identify the
> files as DATAFILES and set SED_OPTIONS appropriately. If it's more
> complicated, you may need to have your filter as a separate script
> submitted into the source pool, which you execute using "sh ..." from
> the Makefile.
>
> For makefile help please mail to buildhelp if need assistance; there
> are examples in the pool of customized makefiles which use specialized
> filters or executables as part of the build process. Look for example
> at the 'zic' or 'tic' code.
Thanks for the tip. While I don't need it at the moment, you never know when I
might.
Yaacov
% -------------------------------------------------
% Yaacov Fenster (603)-881-1154 DTN 381-1154
% [email protected] [email protected]
% Policy 1: All phone calls are to be returned right away.
% Policy 2: All e-mail messages are to be responded to (and hopefully resolved)
% within 24 hours of reading.
% All the opinions voiced are mine alone and do not reflect anyone else's
% opinion. (Including my employer's).
------- End of Forwarded Message
|