Hi Reinhard,

On Wed, Feb 27, 2013 at 12:32:13PM +0100, Reinhard Tartler wrote:
> It turns out that most patches are necessary for fixing the
> automake-based build system. AFAIUI, upstream now prefers the use of
> the CMake Build system, and in fact, most patches are no longer
> necessary when the packaging uses that. Therefore, I have changed the
> packaging to dh7 and cmake. This allowed me to simplify debian/rules
> drastically.

All these changes sound pretty reasonable and provided that Mathieu
confirms his agreement I'd say it makes perfectly sense if you simply
commit your changes into SVN.  Any DD has commit permissions to our
SVN so this should not be a permission problem.

> Also, I had to rework the
> debian/{dcmtk-www,libdcmtk2,libdcmtk2-dev}.install dh_install
> configuration files. I could drop almost all patches. The only patches
> that IMO still make sense are "01_fix_perl_script_path.patch",
> "02_dcmtk_3.6.0-1.patch" and "prefs.patch".

Sounds great.

> The only caveat that I did not manage to implement was the correct
> construction of the dcmtk-doc package, because I was unable to locate
> the relevant calls for invoking doxygen. Therefore, I have removed
> dcmtk-doc from debian/control (it is not relevant to the needs of my
> customer anyways).

Mathieu would you consider checking this out?  I personally also do not
have any cmake / doxygen experience but it would probably not to hard to
do (as last resort with help of debian-mentors).

> Please find the relevant packaging files attached to this email.

Thanks for you patches and as said above please consider direct commit.

Kind regards

       Andreas.





> _______________________________________________
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to