| 1 |
Neil Bothwick <neil <at> digimed.co.uk> writes: |
| 2 |
|
| 3 |
|
| 4 |
> > > I doubt dpkg and rpm aren't going to be much use to you, unless you |
| 5 |
> > > really want to run two package managers. Besides, both are not |
| 6 |
> > > especially useful with the front ends apt* and yum. |
| 7 |
> > |
| 8 |
> > I'd just use those to unpackage and maybe preprocess some of the codes. |
| 9 |
> > |
| 10 |
> > Agreed. I do not want a full blown deb or rpm package manager just |
| 11 |
> > a way to install and evaluate some of those codes before beginning a |
| 12 |
> > more arduous and comprehensive task. |
| 13 |
> |
| 14 |
> In that case you ware deb2targz or rpm2targz to convert the package to a |
| 15 |
> tarball. then you can unpack it and inspect the contents. |
| 16 |
|
| 17 |
|
| 18 |
Agreed. Problem is my workflows it to test as is before looking that the |
| 19 |
codes. If they do not do what they are suppose to (for clustering or HPC) |
| 20 |
then why look under the hood.... Lots of pigs in clustering and HPC, |
| 21 |
the stuff we use to run (and called it distributed or parallel) decades |
| 22 |
ago was much faster..... Putting bloat_ware on top of a cluster is |
| 23 |
just plain stupid and that's what most are doing.... It negates the |
| 24 |
entire point of distributed/hpc, imho. |
| 25 |
|
| 26 |
thx, |
| 27 |
James |
Archives