F
felipe.braun
Guest
Hey all, I've been looking for a way to improve our deployment here, and there is still a question that's been unanswered to me yet. Do we have a way to read the r-code info, specially display-type, by reading the .r file directly? I'm thinking in perl or python, maybe even C or java, if needed. I only found an old project that reads some parts, but only CRC/MD5 info. Explaining in details: since we have a GUI and tty deployment, I have to work with two sets of directories. When our vendor releases a new package update, we get one zip for each. But there are some times that a program is not compiled in tty anymore, since the source changed and it doesn't create a GUI-specific r-code anymore, thus, removing the need to have a tty r-code. When this happens, I end up with an old r-code in tty directory, making the AppServer or batch process read this one instead of the updated file in the GUI directory. The packages are incremental, so not possible to discard the old tty files and have only the new ones. I only thought of a way to get over this by having one set of directories for each package, but it would create a enormous PROPATH (now we have 13 entries in production env, twice for the TTY part, a little more in the dev/staging envs), and it would be awful to manage for each update that we have. I wanted to create a script to read the tty dirs and check the GUI dirs if the files are still GUI only or not, while reading some other info. Spawning a new _progres for each file would not have a good enough performance (more than 57 000 files to check right now), and I had to capture info from stdout/stderr somehow. Doing the reverse approach (_progres spawning a perl script) has the same issue. If there is no other way, I'll do this in steps, working with text files and parsing the content, which I hoped not to do. Thanks!
Continue reading...
Continue reading...