| |
spider-j
Registered: Oct 2004
Posts: 446 |
Release id #233542 : High Voltage SID Collection #79
Hi.
As I can't get https://hvsc.c64.org/download/files/tools/HVSC_Update_Tool_sour.. to compile on my Linux system I'm wondering if it would be easier to write a script that uses the "Update79.hvs" file for update instructions.
Can someone elaborate which the meaning of the what I think to be "commands" is?
I.e. I'm wondering about these constructs:
MOVE
/DEMOS/UNKNOWN/Rockmonitor_Demo.sid
/DEMOS/M-R/Rockmonitor_Tune.sid
REPLACE
/update/fix/DEMOS/M-R/Rockmonitor_Tune.sid
/DEMOS/M-R/
Why the additional step of moving instead of deleting and then copying the updated file into the correct directory?
Also: what about the CREDITS section? Does that mean the update script should just change the original file data?
Would be nice if someone could provide me a list of commands and what each of those should do – and how the data is organized in the "Update79.hvs" file for each of them. So I don't have to figure it all out myself.
Thanks! |
|
| |
ChristopherJam
Registered: Aug 2004
Posts: 1380 |
That archive you linked to contains a HVS_file_format.txt that documents all the commands, if that helps at all. |
| |
spider-j
Registered: Oct 2004
Posts: 446 |
Quote: That archive you linked to contains a HVS_file_format.txt that documents all the commands, if that helps at all.
Ah, yeah. Didn't see this one. That should help!
Thanks! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11136 |
Wouldn't it be much easier to just download the whole package? |
| |
spider-j
Registered: Oct 2004
Posts: 446 |
Quote: Wouldn't it be much easier to just download the whole package?
Well, that is what I did in the past. But I started my own MYSQL database for some kind of "private" HVSC search site and rewriting every DB entry from scratch takes a very long time. I'd like to avoid that. |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
> Why the additional step of moving instead of deleting and then copying the updated file into the correct directory?
The hvs script is used by Perff to update the CSDb sid entries too.
I fear there is nothing written about it but IIRC, it's a deal we had with Perff for keeping the CSDb entries for sid tunes and just rename/move them, else the whole entry and its comments would be lost on a DELETE command. |
| |
spider-j
Registered: Oct 2004
Posts: 446 |
Quoting iAN CooGI fear there is nothing written about it but IIRC, it's a deal we had with Perff for keeping the CSDb entries for sid tunes and just rename/move them, else the whole entry and its comments would be lost on a DELETE command.
Okay, that makes sense. Thank you for that info! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11136 |
brainfart: you could put the hvsc into a git repo. then when a new one is released, just download the entire package and commit it. now you can parse the commit history, which will show you all files that changed, no matter if they moved or what ever. might be easier than trying to figure out the weird format of the update files :) |
| |
TheRyk
Registered: Mar 2009
Posts: 2076 |
actually I'm one of the whackos doing the update.exe instead of whole package and never had any trouble with it, but (after some short gnome episode) I'm just a win-doomed idiot, patting my shoulder for causing less CO2 by just leeching the update ;)
@GIT repo: of course this would work... but it would kill the tradition of half year waiting for next update, you MADMAN! |
| |
spider-j
Registered: Oct 2004
Posts: 446 |
Quoting TheRyk@GIT repo: of course this would work... but it would kill the tradition of half year waiting for next update, you MADMAN!
I think what GPZ meant was an idea for me to (ab)use a local git repository to get a better machine readable diff output between HVSC releases than the official *.hvs file :-) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11136 |
Quote:I think what GPZ meant was an idea for me to (ab)use a local git repository to get a better machine readable diff output between HVSC releases than the official *.hvs file :-)
yes, indeed. That the collection as such should have been put into a proper repo 10+ years ago is an entire different topic =D |
