Hello Mike,
if memory serves me correctly, the "clean" option
of typical Makefiles removes "core dumps",
*files* that are named "core". In the case of OCF, "core" is
a *directory* which requires different options for "rm"
to be removed.
If your Makefile says "rm -f core" in the directory where
core dumps are expected, no directory named core will be removed.
Regarding your OS sources tree I guess that for each separate
branch you use a specific Makefile, so branch specific problems
could be solved there.
Hope I didn't misunderstand you.
Regards,
Daniel Ciesinger
____________________________ Antwort-Abtrennung ________________________________
Betreff: Re: [OCF] Renaming OCF "core" directory
Autor: MIME:[EMAIL PROTECTED] bei INTERNET
Datum: 06.08.99 01:42
Thomas,
> if I understand you right, you have the directory named "core" only on your
> development machines, but you would only have a JAR-file on the systems you
> deliver to your customers. Normally, it should not be necessary to run a
> program from the parent directory of "core", i.e. the directory "opencard".
>
> Is my interpretation correct, that problems would only occur when somebody
> runs a program from the "opencard" directory of the opencard source tree on
> one of your development machines and that program crashes ? In that case,
> the current directory structure would seem quite acceptable to me.
The problem I'm running into is that the OCF sources are in the
same source tree as all the rest of our Solaris UNIX sources (since
we are shipping OCF as a system service in our next OS release).
The keepers of the UNIX sources have several rules for sources that
are included in the OS source tree, one of which is that no files
or directories can be named "core", since over the years many scripts
have been written to look for and remove files and directories
called "core" as part of the software build and release process.
>From a customer perspective, this isn't an issue since we only
ship a jar file with the OCF classes in it.
> Renaming all packages would cause significant work for us to change the
> opencard implementation as well for all application programmers who would
> need to update all their OCF applications. Therefore, I would like to leave
> the OCF package names as they are.
We could all decide that OCF V2.0 makes the package name change.
Are there a lot of people using OCF in a production environment
yet?
Anyway, I'm just collecting feedback from people on this to see if
it's worth even submitting an RFE.
mike
--
----------------------------------------------------------------------------
Michael Bender E-Mail: [EMAIL PROTECTED]
Sun Microsystems, Inc. Tel: 650-786-0498
901 San Antonio Road Tel Pager: 888-423-9066
Palo Alto, CA 94303-4900 URL Pager: http://www.skytel.com/Paging/
Mailstop: UMPK18-110 Pager PIN: 4239066
----------------------------------------------------------------------------
Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for access
to documentation, code, presentations, and OCF announcements.
-----------------------------------------------------------------------------
To unsubscribe from the OCF Mailing list, send a mail to
"[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
message.
{\rtf1\ansi \deff0\deflang1024{\fonttbl{\f0\froman Tms Rmn;}{\f1\froman Symbol;}{\f2\fswiss Helv;}}
{\colortbl;\red0\green0\blue127;\red0\green127\blue0;\red0\green127\blue127;\red127\green0\blue0;
\red127\green0\blue127;\red127\green127\blue0;\red127\green127\blue127;;\red0\green0\blue255;
\red0\green255\blue0;\red0\green255\blue255;\red255\green0\blue0;\red255\green0\blue255;
\red255\green255\blue0;\red255\green255\blue255;}\paperw12240\paperh15840\margl1800\margr1800\margt1440\margb1440
\gutter0 \defformat\sectd \pard\plain {\plain \f0 \cb7 \cf0 \cb1 \cf7 \cb7 \cf0 Hello Mike,\
\cb1 \cf7 \
\cb1 \cf7 \cb7 \cf0 if memory serves me correctly, the "clean" option\
\cb1 \cf7 \cb7 \cf0 of typical Makefiles removes "core dumps",\
\cb1 \cf7 \cb7 \cf0 *files* that are named "core". In the case of OCF, "core" is\
\cb1 \cf7 \cb7 \cf0 a *directory* which requires different options for "rm"\
\cb1 \cf7 \cb7 \cf0 to be removed.\
\cb1 \cf7 \
\cb1 \cf7 \cb7 \cf0 If your Makefile says "rm -f core" in the directory where\
\cb1 \cf7 \cb7 \cf0 core dumps are expected, no directory named core will be removed.\
\cb1 \cf7 \
\cb1 \cf7 \cb7 \cf0 Regarding your OS sources tree I guess that for each separate\
\cb1 \cf7 \cb7 \cf0 branch you use a specific Makefile, so branch specific problems\
\cb1 \cf7 \cb7 \cf0 could be solved there.\
\cb1 \cf7 \
\cb1 \cf7 \cb7 \cf0 Hope I didn't misunderstand you.\
\cb1 \cf7 \
\cb1 \cf7 \cb7 \cf0 Regards,\
\cb1 \cf7 \cb7 \cf0 Daniel Ciesinger\
\cb1 \cf7 \
\
\
\cb1 \cf7 ____________________________ Antwort-Abtrennung ________________________________\
\cb1 \cf7 Betreff: Re: [OCF] Renaming OCF "core" directory\
\cb1 \cf7 Autor: MIME:[EMAIL PROTECTED] bei INTERNET\
\cb1 \cf7 Datum: 06.08.99 01:42\
\
\
\cb1 \cf7 Thomas,\
\cb1 \cf7 \
\cb1 \cf7 > if I understand you right, you have the directory named "core" only on your \
\cb1 \cf7 > development machines, but you would only have a JAR-file on the systems you \
\cb1 \cf7 > deliver to your customers. Normally, it should not be necessary to run a\
\cb1 \cf7 > program from the parent directory of "core", i.e. the directory "opencard". \
\cb1 \cf7 > \
\cb1 \cf7 > Is my interpretation correct, that problems would only occur when somebody \
\cb1 \cf7 > runs a program from the "opencard" directory of the opencard source tree on \
\cb1 \cf7 > one of your development machines and that program crashes ? In that case,\
\cb1 \cf7 > the current directory structure would seem quite acceptable to me.\
\cb1 \cf7 \
\cb1 \cf7 The problem I'm running into is that the OCF sources are in the \
\cb1 \cf7 same source tree as all the rest of our Solaris UNIX sources (since \
\cb1 \cf7 we are shipping OCF as a system service in our next OS release). \
\cb1 \cf7 The keepers of the UNIX sources have several rules for sources that \
\cb1 \cf7 are included in the OS source tree, one of which is that no files\
\cb1 \cf7 or directories can be named "core", since over the years many scripts \
\cb1 \cf7 have been written to look for and remove files and directories\
\cb1 \cf7 called "core" as part of the software build and release process.\
\cb1 \cf7 \
\cb1 \cf7 From a customer perspective, this isn't an issue since we only \
\cb1 \cf7 ship a jar file with the OCF classes in it.\
\cb1 \cf7 \
\cb1 \cf7 > Renaming all packages would cause significant work for us to change the\
\cb1 \cf7 > opencard implementation as well for all application programmers who would\
\cb1 \cf7 > need to update all their OCF applications. Therefore, I would like to leave \
\cb1 \cf7 > the OCF package names as they are.\
\cb1 \cf7 \
\cb1 \cf7 We could all decide that OCF V2.0 makes the package name change. \
\cb1 \cf7 Are there a lot of people using OCF in a production environment \
\cb1 \cf7 yet?\
\cb1 \cf7 \
\cb1 \cf7 Anyway, I'm just collecting feedback from people on this to see if \
\cb1 \cf7 it's worth even submitting an RFE.\
\cb1 \cf7 \
\cb1 \cf7 mike\
\cb1 \cf7 \
\cb1 \cf7 -- \
\cb1 \cf7 ----------------------------------------------------------------------------\
\cb1 \cf7 \cb1 \cf7 Michael Bender E-Mail: [EMAIL PROTECTED] \
\cb1 \cf7 \cb1 \cf7 Sun Microsystems, Inc. Tel: 650-786-0498\
\cb1 \cf7 \cb1 \cf7 901 San Antonio Road Tel Pager: 888-423-9066\
\cb1 \cf7 \cb1 \cf7 Palo Alto, CA 94303-4900 URL Pager: http://www.skytel.com/Paging/ \
\cb1 \cf7 \cb1 \cf7 Mailstop: UMPK18-110 Pager PIN: 4239066\
\cb1 \cf7 ---------------------------------------------------------------------------- \
\cb1 \cf7 Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for access \
\cb1 \cf7 to documentation, code, presentations, and OCF announcements. \
\cb1 \cf7 ----------------------------------------------------------------------------- \
\cb1 \cf7 To unsubscribe from the OCF Mailing list, send a mail to \
\cb1 \cf7 "[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the \
\cb1 \cf7 message.\
\cb1 \cf7 \
\par }}-
