various packaging issues

[Dave Love]

I was looking at making packages for HPC-related stuff I'm familiar with
and I'm wondering how to translate features of the rpm or dpkg packaging
that I understand.  I couldn't see answers in the doc or immediately
find examples; apologies if I've missed something obvious.

* I should specify a disjunction of licences like "BSD or GPLv2" rather
  than the conjunction, which seems to be represented as a list (though
  the doc doesn't say what a list represents).  I.e. in Fedora-ish
  rpm-speak, I have A or B, rather than C and D.  Is that possible?

* RPM specs commonly have multiple sources specified, e.g. source and
  doc or example tarballs, or configuration files of some kind which
  aren't patches.  Is there a way to do that?

* What if I effectively have multiple build systems?  For instance a
  python interface needs to be built with an explicit
  "python... setup.py" with an overall autotools build.  While I figured
  out how to build and install in that situation, at least for one
  python, it looks messy.  I wonder what the recommended way is,
  particularly to provide python2 and python3 modules, or for other
  things like Java or Perl components.