Hi,

Reinhard Tartler wrote:

>    * don't try to install non-existing documentation, fixes FTBFS on powerpc
>    * add NEWS.Debian file
>    * install doc/APIChanges and refer to them in NEWS.Debian (Closes: #623682)
>    * readd deprecated avcodec_thread_init in libavformat

Thanks for this.  I tried the package and it seems that NEWS.Debian
isn't actually installed.  While working on that, I picked a few other
nits:

 * the APIChanges should only be relevant to people using the
   development libraries, so I think it makes more sense to only
   install them to lib*-dev and libav-doc

 * using source format 3.0 (quilt), so "git reset --hard" and
   other habits don't produce confusing results

 * allowing "debian/rules clean" as a non-root user.  In
   modern times, most people don't run "debian/rules binary" as true
   root anyway, and in the worst case "debian/rules clean" will error
   out and the user will know what to do (just a pet peave).

If you have any complaints, I'd be glad to roll a new version of the
patches addressing them.

Thoughts?
Jonathan Nieder (3):
  clean up NEWS.Debian and related documentation
  use source format 3.0 (quilt)
  debian/rules: allow clean as non-root

 Doxyfile                   |    2 +-
 debian/NEWS.Debian         |   18 ------------------
 debian/README.Debian       |    9 +++++++++
 debian/changelog           |   10 ++++++++++
 debian/control             |    1 -
 debian/libavcodec-dev.NEWS |    9 +++++++++
 debian/rules               |   16 ++++++++--------
 debian/source/format       |    2 +-
 libavcodec/avcodec.h       |    2 +-
 libavcodec/utils.c         |    2 +-
 libavcodec/version.h       |    3 +++
 11 files changed, 43 insertions(+), 31 deletions(-)
 delete mode 100644 debian/NEWS.Debian
 create mode 100644 debian/libavcodec-dev.NEWS

-- 
1.7.5




_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers

Reply via email to