i just ran my update script and saw this go flashing by... not sure how to handle it or if i need to do anything because of it...
cvs update -d xtrn
[...]
cvs update: Updating xtrn/lord
U xtrn/lord/ansi2lord.js
cvs update: move away `xtrn/lord/badsay.lrd'; it is in the way
cvs update -d xtrn
[...]
cvs update: Updating xtrn/lord
U xtrn/lord/ansi2lord.js
cvs update: move away `xtrn/lord/badsay.lrd'; it is in the way
Try just running "cvs update -C" in the xtrn/lord dir.
I don't know why that happens sometimes, but the xtrn/lord/CVS/Entries fileseems to have not gotten updated.
Re: updating from CVS
By: Digital Man to Rampage on Sun Sep 01 2019 13:42:15
cvs update -d xtrn
[...]
cvs update: Updating xtrn/lord
U xtrn/lord/ansi2lord.js
cvs update: move away `xtrn/lord/badsay.lrd'; it is in the way
Try just running "cvs update -C" in the xtrn/lord dir.
done...
cvs update -C
? 3RDPARTY.DAT
? BADSAY.DAT
? BADWORDS.DAT
? BUGRPT.FRM
? DOATTRIB.BAT
? DSTART
? EVENTS.LDY
? GARDEN.TXT
? GOODSAY.DAT
? IGMSEC.INI
? LADY.DOC
? LENEMY.DAT
? LGAMETXT.DAT
? LOCKOUT.DAT
? LOCKOUT.TXT
? LORD.DOC
? LORD.EXE
? LORD.LDY
? LORD.OVR
? LORDCFG.EXE
? LORDEXT.DAT
? LORDRIP.DAT
? LORDSTRC.PAS
? LORDTXT.DAT
? NOATTRIB.BAT
? NORMSAY.DAT
? PLAYEXT.DAT
? REGISTER.DOC
? START1
? START2
? START3
? START4
? START5
? TROUBLE.TXT
? bar.txt
? darkbar.txt
? lognow.txt
? logold.txt
? lord.bat
? lord.dat
? mail0.dat
? node1.dat
? node10.dat
? node2.dat
? node3.dat
? node4.dat
? node5.dat
? node6.dat
? node7.dat
? node8.dat
? node9.dat
? player.dat
? playext2.dat
? start.bat
? temp-1
? time.dat
cvs update: Updating .
P lordtxt.lrd
cvs update: Updating aratime
cvs update: Updating barak
I don't know why that happens sometimes, but the xtrn/lord/CVS/Entries fileseems to have not gotten updated.
interesting... i'll keep an eye on it the next time i update...
Oh, wow, it appears you have an actual LORD installation in xtrn/lordmixed
with check-outs from CVS?!?
Thatinteresting... i'll keep an eye on it the next time i update...
I didn't realize you already had a regulard LORD install in xtrn/lord.
was the issue. And I think you just hosed it with those files from CVS(for
JSLORD) which are not necessarily compatible with the real LORD executables. :-(
i had forgotten all about having put it in xtrn with the other games... geez... it was an existing game from one of the other BBSes running here anyway... hardly ever got used other than a few times by myself and the girls when they were here... i'll move it (later) and copy the files back over from the other system... oh well :sigh:
i had forgotten all about having put it in xtrn with the other games... geez... it was an existing game from one of the other BBSes running here anyway... hardly ever got used other than a few times by myself and the
girls when they were here... i'll move it (later) and copy the files back over from the other system... oh well :sigh:
In my directory structure, I normally keep all of my non-Synchronet related doors in my D:\BBS\DOORS directory.
Rampage wrote to Nightfox <=-
In my directory structure, I normally keep all of my
non-Synchronet related doors in my D:\BBS\DOORS directory.
no such location on linux... but yes, i do understand what you
are saying... i had considered to do that when i set up those
DOSemu doors but decided that consistency was the better way to
go and since all the other doors are in xtrn... well, you can see
what happened... in this case, the game in question is not played
very often... maybe a dozen times in the year it has been
configured... it is no big loss, though...
In my directory structure, I normally keep all of my non-Synchronet related N>> doors in my D:\BBS\DOORS directory.
no such location on linux... but yes, i do understand what you are saying... i had considered to do that when i set up those DOSemu doors but decided that consistency was the better way to go and since all the other doors are in xtrn... well, you can see what happened... in this case, the game in question is not played very often... maybe a dozen times in the year it has been configured... it is no big loss, though...
i am considering what to do... the ultimate best way would be to keep the CVS tree completely separate from the actual BBS installation but that's a lot more work to deal with... things like this are learned over time...
go and since all the other doors are in xtrn... well, you can see
what happened... in this case, the game in question is not played
very often... maybe a dozen times in the year it has been
configured... it is no big loss, though...
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.
In my directory structure, I normally keep all of my non-Synchronet
related doors in my D:\BBS\DOORS directory.
no such location on linux... [...]
I'm not sure what you mean by "no such location on linux"..
mark lewis wrote to Gamgee <=-
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.
yeah, that might be what i do... seems legit, anyway ;)
If/when I get around to installing the ported JS version, it will
likely go into ../sbbs/xtrn/lordjs.
if you are pulling from CVS, it is already there as xtrn/lord
which is how we got here -=B-)
I'm not sure what you mean by "no such location on linux"..
no drive letters on linux... no matter how many drives you have, they are all under / and are generally devoted to specific directory trees... drive letters on linux only exist in DOSemu and then the game is accessed in plain old D:\ IIRC...
On 2019 Sep 02 09:36:00, you wrote to Rampage:
go and since all the other doors are in xtrn... well, you can see
what happened... in this case, the game in question is not played
very often... maybe a dozen times in the year it has been
configured... it is no big loss, though...
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.
yeah, that might be what i do... seems legit, anyway ;)
If/when I get around to installing the ported JS version, it will likely go into ../sbbs/xtrn/lordjs.
if you are pulling from CVS, it is already there as xtrn/lord which is how we got here -=B-)
mark lewis wrote to Gamgee <=-
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.
yeah, that might be what i do... seems legit, anyway ;)
If/when I get around to installing the ported JS version, it will likely go into ../sbbs/xtrn/lordjs.
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... I've been updating from CVS, most recently this past
Saturday 8/31. I don't have the new JSLord though, not in
/sbbs/xtrn anyway. I'm not very up to speed on the CVS stuff, but
should I be getting that when I do the updates? I do the exact
procedure as shown on the Wiki. Does it (/sbbs/xtrn/lord) have to
already exist for CVS to "give" it to me?
Digital Man wrote to Gamgee <=-
If/when I get around to installing the ported JS version, it will likely go into ../sbbs/xtrn/lordjs.
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... I've been updating from CVS, most recently this past
Saturday 8/31. I don't have the new JSLord though, not in
/sbbs/xtrn anyway. I'm not very up to speed on the CVS stuff, but
should I be getting that when I do the updates? I do the exact
procedure as shown on the Wiki. Does it (/sbbs/xtrn/lord) have to
already exist for CVS to "give" it to me?
You have to use "cvs update -d" (not the '-d') for it to create
new directories.
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: | BrokenMind |
---|---|
Location: | Central Pennsylvania United States |
Users: | 60 |
Nodes: | 4 (0 / 4) |
Uptime: | 58:26:01 |
Calls: | 177 |
Files: | 2,017 |
Messages: | 20,571 |