WISHLIST:
- cross-compiler support
- "Simple Packaging Kit" output support see
  http://developer.stampede.org/system/spk/
  (as a frontend and a backend... maybe)
  (also: need to decide if we should `spk_build' or just
  implement it ourself w/ tar and bzip2..
  i think we oughta implement it ourselves)
- automatically add conflicts if file sets intersect
- we support the default debian changelog format, but observing
  all of Section 3.2.3. of /usr/share/doc/packaging-manual/packaging.text
  is undone (there are many specifics to carefully check)
- warn about installed files that are never used.
- implement Slava Gorbanev's <rnd@web-drive.ru> suggestion
  for multiple build support in RPM:

      i suggest use conditional macros, consider following in your .spec:

      Release: 1%{?debug}
      # %{?debug} means "substitute %debug expansion if it's not empty, and
      # nothing otherwise"
      ...
      %build
      ./configure %{?debug:--enable-debug}
      # similar, this means "substitute string after ':' 
      # if %debug yields non-null, nothing otherwise"
      # note you could invert condition sense with %{!?debug:something} --
      # substitute 'something' if debug IS null.
      # note also that substituted string can contain macros itself.
      ...

      then, "nondebug" package build as usual, while "debugging" should be built
      with 'rpm --define "debug 1"'.  thus you'll get two releases, xxx-1 and
      xxx-1debug.  there are two .src.rpms still, but one .spec for both.