Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> I see you are doing more than I thought you were doing > > rpms and debs are both cpio files so the easy way is to unpack them and > see what's going on: > > rpm2cpio name.rpm | cpio -iv --make-directories > dpkg -x somepackage.deb ~/temp/ > > Considering the size of what you are doing, you are probably better off > running a Centos and Debian system to evaluate the code and discard the > rubbish. Once you've isolated the interesting ones, you can evaluate > them closer and maybe write ebuilds for them. Workflow is the first test. Second unpack and look at the code to maybe 5% of what I test. The tests I'm developing are low level code profiling. Once I figure it all out what I need manually looking at many (cluster/hpc) codes, then I hope to use CI to automate the process of first performance profiling the codes. THEN unpack and look at the codes iff it is impressive on performance. I am leaning towards a separate box for these evaluations, but a VM environment might be better in the long run... dunno.... thx, James
