The real problem is not whether you can handle multiple formats, it's conflicts. Consider that package A wants libfoo.1.1.1 with --extra-foo turned on and nothing else, but package B wants libfoo.1.1.1 with --mini-foo turned on and nothing else. Using either version of libfoo.1.1.1 will break one of A or B. So, if you want to install packages meant for RedHat along with ones meant for Debian, or Suse, or... you're going to run into this sort of problem *very* quickly. Unless they've somehow solved this, this project isn't really what a lot people might want. Of course the folks over at autopackage provide a solution of sorts, but that must be implemented at the software package producer end, not at the comsumers end, so unless the producer co-operates (yeah, right) the consumer is SOL.
The real problem is not whether you can handle multiple formats, it's conflicts. Consider that package A wants libfoo.1.1.1 with --extra-foo turned on and nothing else, but package B wants libfoo.1.1.1 with --mini-foo turned on and nothing else. Using either version of libfoo.1.1.1 will break one of A or B. So, if you want to install packages meant for RedHat along with ones meant for Debian, or Suse, or ... you're going to run into this sort of problem *very* quickly. Unless they've somehow solved this, this project isn't really what a lot people might want. Of course the folks over at autopackage provide a solution of sorts, but that must be implemented at the software package producer end, not at the comsumers end, so unless the producer co-operates (yeah, right) the consumer is SOL.
Closing of the American Mind