Re: cvswrappers and import command line conflict???

2004-03-05 Thread Eric Siegerman 
On Wed, Mar 03, 2004 at 09:43:56AM -0500, Larry Jones wrote:
> I don't think so -- have you tried it?

Woops, you're right!  I knew I'd accomplished it; shame on me for
describing how from (what turned out to be completely fictional
and bogus) memory.

What I *actually* did (and this time I have verified it) was to
put this line at the bottom of my ~/.cvswrappers:
* -k 'o'

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: cvswrappers and import command line conflict???

2004-03-04 Thread Larry Jones 
Eric Siegerman writes:
> 
> Try putting -ko in your ~/.cvsrc (look up the syntax in the
> manual); then don't specify any -k variant on the command line.
> That way it'll be the -kb in cvswrappers that takes precedence.

I don't think so -- have you tried it?

-Larry Jones

What this games needs are negotiated settlements. -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: cvswrappers and import command line conflict???

2004-03-03 Thread Eric Siegerman 
On Tue, Mar 02, 2004 at 09:23:43AM -0500, Timothy Stone wrote:
> $ cvs -d $REP import -ko -I! -m "some meaningful message" blojsom
> BLOJSOM REL_2_11
> 
> Basically, the "-ko" switch seems to be hosing the JAR files in the
> project. Everything gets a Sticky Option of -ko. This kills JARs.

Yup.  The -ko on the command line overrides the -kb in
cvswrappers.

Try putting -ko in your ~/.cvsrc (look up the syntax in the
manual); then don't specify any -k variant on the command line.
That way it'll be the -kb in cvswrappers that takes precedence.

(No comment on your -W approach; I've never tried it, so I have
to take your word for it that it doesn't work.)

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: cvswrappers and import command line conflict???

2004-03-02 Thread Larry Jones 
Timothy Stone writes:
> 
> $ cvs -d $REP import -ko -I! -m "some meaningful message" blojsom 
> BLOJSOM REL_2_11
> 
> Basically, the "-ko" switch seems to be hosing the JAR files in the 
> project. Everything gets a Sticky Option of -ko. This kills JARs.

Yep.  An explicit -k option on the command line overrides the implied -k
options from wrappers.  Wrappers are processed in order so you should be
able to do what you want with:

cvs import -W "*.jar -k 'b'" -W "* -k 'o'" ...

-Larry Jones

I sure like summer vacation. -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: cvswrappers and import command line conflict???

2004-03-02 Thread Jim.Hyslop 
Timothy Stone wrote:
> My import:
> 
> $ cvs -d $REP import -ko -I! -m "some meaningful message" blojsom 
> BLOJSOM REL_2_11
> 
> Basically, the "-ko" switch seems to be hosing the JAR files in the 
> project. Everything gets a Sticky Option of -ko. This kills JARs.
Well, what did you expect? You *told* CVS to use the -ko option for all
files on the import. This overrides the defaults.

http://www.cvshome.org/docs/manual/cvs-1.11.13/cvs_16.html#SEC139


-- 
Jim Hyslop 
Senior Software Designer 
Leitch Technology International Inc. () 
Columnist, C/C++ Users Journal () 




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs