if you are pulling from CVS, it is already there as xtrn/lord
which is how we got here -=B-)
Hmmmm.... that provides me a good opportunity to ask this
question... [...]
mark lewis wrote to Gamgee <=-
if you are pulling from CVS, it is already there as xtrn/lord
which is how we got here -=B-)
Hmmmm.... that provides me a good opportunity to ask this
question... [...]
ummm... cvs update -d xtrn
i forget when DM mentioned this but it is part of my standard
update mechanism... IIRC -d adds (and removes??) new
directories...
What about all the other directories under /sbbs ? The update
procedure on the Wiki only shows "cvs update -d src 3rdp".
Do we also need to do "ctrl data exec text web xtrn" when updating?
(I know we just mentioned xtrn, and the exec/text are done later in
the Wiki procedure). Does it hurt anything to do all of them every
time?
mark lewis wrote to Gamgee <=-
if you are pulling from CVS, it is already there as xtrn/lord
which is how we got here -=B-)
Hmmmm.... that provides me a good opportunity to ask this
question... [...]
ummm... cvs update -d xtrn
i forget when DM mentioned this but it is part of my standard
update mechanism... IIRC -d adds (and removes??) new
directories...
OK, that makes good sense, I'll do that soonly.
What about all the other directories under /sbbs ? The update
procedure on the Wiki only shows "cvs update -d src 3rdp". Do we
also need to do "ctrl data exec text web xtrn" when updating?
(I
know we just mentioned xtrn, and the exec/text are done later in
the Wiki procedure). Does it hurt anything to do all of them
every time?
mark lewis wrote to Gamgee <=-
What about all the other directories under /sbbs ? The update
procedure on the Wiki only shows "cvs update -d src 3rdp".
remember, those are examples and may be used or not... the main
gist, though, is which ones to use... i prefer to list each
separately for my logging analysis...
Do we also need to do "ctrl data exec text web xtrn" when updating?
certainly not ctrl! you'll wipe out your configuration...
(I know we just mentioned xtrn, and the exec/text are done later in
the Wiki procedure). Does it hurt anything to do all of them every
time?
my update script does them all every time...
SDATE1=$(date +"%s")
EXECDATE=$(date --date="@$SDATE1" '+%Y%m%d%H%M')
[...]
tar -czf ctrl_$EXECDATE.tgz ctrl
tar -czf exec_$EXECDATE.tgz exec
cvs update -d exec
cvs update -d src
cvs update -d 3rdp
cvs update -d xtrn
Do we also need to do "ctrl data exec text web xtrn" when updating?
certainly not ctrl! you'll wipe out your configuration...
Yes, understood. I always do a safety script first that copies
all my .ini's somewhere safe. But... one reason you would need to
do ctrl is to get new versions of certain things in there. For
example, there have recently been a lot of things/options added to modopts.ini. I realize you'd have to go back into it and edit in
any previous changes you made, but how else will you ever get a
newer version? Also, this is where text.dat resides, although I
do that one manually as suggested on the Wiki.
(I know we just mentioned xtrn, and the exec/text are done later in
the Wiki procedure). Does it hurt anything to do all of them every
time?
my update script does them all every time...
SDATE1=$(date +"%s")
EXECDATE=$(date --date="@$SDATE1" '+%Y%m%d%H%M')
[...]
tar -czf ctrl_$EXECDATE.tgz ctrl
tar -czf exec_$EXECDATE.tgz exec
cvs update -d exec
cvs update -d src
cvs update -d 3rdp
cvs update -d xtrn
I think text is another that needs to be done, right? The update directions certainly say to do it.
Thanks for the input.
mark lewis wrote to Gamgee <=-
What about all the other directories under /sbbs ? The update procedure on the Wiki only shows "cvs update -d src 3rdp".
remember, those are examples and may be used or not... the main
gist, though, is which ones to use... i prefer to list each
separately for my logging analysis...
Do we also need to do "ctrl data exec text web xtrn" when updating?
certainly not ctrl! you'll wipe out your configuration...
Yes, understood. I always do a safety script first that copies
all my .ini's somewhere safe. But... one reason you would need to
do ctrl is to get new versions of certain things in there.
For
example, there have recently been a lot of things/options added to modopts.ini. I realize you'd have to go back into it and edit in
any previous changes you made, but how else will you ever get a
newer version?
Also, this is where text.dat resides, although I
do that one manually as suggested on the Wiki.
I'd suggest adding a version number to the directory for the
doors, if needed. For example my "regular" LORD is installed in ../sbbs/xtrn/lord406. If/when I get around to installing the
ported JS version, it will likely go into ../sbbs/xtrn/lordjs.
Digital Man wrote to Gamgee <=-
What about all the other directories under /sbbs ? The update
procedure on the Wiki only shows "cvs update -d src 3rdp". Do we
also need to do "ctrl data exec text web xtrn" when updating?
"ctrl" - never
"data" - no (it's not in CVS)
"exec" - always
"text" - depends on whether you have local changes or not, you
probably do "web" - likely, yes
"xtrn" - with care
know we just mentioned xtrn, and the exec/text are done later in
the Wiki procedure). Does it hurt anything to do all of them
every time?
Yes, it would hurt to synchronize all of those sub-dirs from CVS.
mark lewis wrote to Gamgee <=-
do ctrl is to get new versions of certain things in there. For
example, there have recently been a lot of things/options added to modopts.ini. I realize you'd have to go back into it and edit in
any previous changes you made, but how else will you ever get a
newer version? Also, this is where text.dat resides, although I
do that one manually as suggested on the Wiki.
i go over the cvs log entries... when i see something for
modopts.ini, i look at the file in CVS and manually compare it to
mine... then i add the stuff mine is missing...
I think text is another that needs to be done, right? The update directions certainly say to do it.
the above is right out of my script... i don't think i've ever
updated text at all... that's something i might have to look at
but if it is done, it would need extreme care since you are free
to change those files as you see fit...
Digital Man wrote to Gamgee <=-
Re: Re: updating from CVS
certainly not ctrl! you'll wipe out your configuration...
Yes, understood. I always do a safety script first that copies
all my .ini's somewhere safe. But... one reason you would need to
do ctrl is to get new versions of certain things in there.
Normally, you don't need to do that.
For
example, there have recently been a lot of things/options added to modopts.ini. I realize you'd have to go back into it and edit in
any previous changes you made, but how else will you ever get a
newer version?
You don't need them. For modopts.ini, a missing section or value
just means that module will use its default option values.
Also, this is where text.dat resides, although I
do that one manually as suggested on the Wiki.
Yup, if you have modifications to the text.dat. Otherwise, you
can overwrite the file with the one from CVS or just replace with
with a 0-byte file and you'll always get the default text strings built-into sbbs.
Sysop: | KrAAB |
---|---|
Location: | Donna, TX |
Users: | 3 |
Nodes: | 20 (0 / 20) |
Uptime: | 06:47:29 |
Calls: | 478 |
Files: | 2,001 |
Messages: | 41,897 |