For the next (testing) version, maybe a script to merge (update) pmagic would be useful.
The user would download the version / release of pmagic on his own and then expand its content in, say, "
If UBCD is expanded in "
The script would first delete "
Then a "sed" script would change "
Optionally, the script could update main.cfg to reflect the new pmagic version (according to the new PMAGIC_*.SQFS file). This is not essential, but convenient
Basically, the same scripting techniques are already being used in other scripts in UBCD. It is possible that Victor already uses at least part of these concepts in his own script(s).
Thoughts? Comments? Volunteers?
ps: In this post, I used a mix of "/" and "\". I think the intention is clear anyway, and there would be respective scripts for "Win32" and for "Linux", just as other scripts in UBCD.
The user would download the version / release of pmagic on his own and then expand its content in, say, "
c:\pmagic-extracted\".
If UBCD is expanded in "
c:\ubcd-extracted\", the script would be executed as:
Code:
pm2ubcd "c:\pmagic-extracted\" "c:\ubcd-extracted\"
indicating the origin (source) of the new pmagic version, and the destination directory (adding "/pmagic/" to the latter).The script would first delete "
c:\ubcd-extracted\pmagic\pmodules\PMAGIC_*.SQFS", and then copy the new files to their respective locations (overwriting the old ones).
Then a "sed" script would change "
/pmagic/boot/syslinux/*.cfg" (according to the pm2ubcd command line argument) regarding:
Code:
_ "F1 (-F12) /pmagic/boot/syslinux/message*.txt"
_ "/pmagic/initrd.img " ==>> "/pmagic/initrd.img iso_filename=ubcd<version_number>.iso"
_ "/pmagic/initrd.img " ==>> "/pmagic/initrd.img iso_filename=ubcd<version_number>.iso"
Optionally, the script could update main.cfg to reflect the new pmagic version (according to the new PMAGIC_*.SQFS file). This is not essential, but convenient
Basically, the same scripting techniques are already being used in other scripts in UBCD. It is possible that Victor already uses at least part of these concepts in his own script(s).
Thoughts? Comments? Volunteers?
ps: In this post, I used a mix of "/" and "\". I think the intention is clear anyway, and there would be respective scripts for "Win32" and for "Linux", just as other scripts in UBCD.