Gilbert Rebhan wrote:
Hi!
> Alexander Wagner schrieb:
>> Well, in case you really always want to use the bleeding
>> edge co the cvs version to some dir and use some wrapper
>> script to fire it up right from there:
>>
>> ----------------------------------------------------------------------
>> #!/bin/sh
>> cd $HOME/sourceforge/scid/
>> cvs update
>> export PATH=.:$PATH
>> rm scid
>> make
>> export file=`echo "$1" | sed -e 's/\..*$//'`
>> exec ./sc_remote "$file"
>> ----------------------------------------------------------------------
>>
>
>> But beware, cvs might be broken, so <put your favourite
>> disclaimer here/> and re-read it at each startup ;)
>>
>
> i'll not use it always, only if there's a feature i won't
> wait for until the next release comes up ...
Then just leave out the cvs update line. Just add a # in
front of the line to disable it.
> your script don't work, i need the $CVSROOT =
Nope. It just requires that you did a co first. Then the
local cvs should know where the repository is located. Just
cvs co from scid.sf.net manually, then also the update will
work. Of course you can not update a tree that was not
checked out. So, first run
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/scid login
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/scid co
-P scid
Then you can use the above cvs update stanza.
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
