Packaging a difficult project

Hi all, I have a software project that I plan on creating Debian packages for which is non-standard in that it uses patched versions of GCC and Doxygen. http://edoc.sourceforge.net/ --- Project Description --- EDoc++ is a compile time C++ exception analysis/documentation tool. EDoc++ is a tool

Re: Creating Source Packages

> > Take a look at > http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#native_vs_non_native > and the question after that ("What's wrong with upstream shipping a debian/ > directory?"). > Yep, all sound like good reasons to separate the source distfile and the debian specific data. Curr

Re: Creating Source Packages

> Actually, there is no one-file source package form of a deb like there > is for rpms. When you create your binary package, a signed .dsc file is > created with which you can create the deb in conjunction with the > original upstream tarball and the diff of the debian packaging. > Ahh that would

Creating Source Packages

Hi all, I have been looking on the web, but have found little in the way of tutorials on how to create a debian source package. I have created a binary package for my project (EDoc++: http://edoc.sourceforge.net/), but want to create a source package and then build the binary one from this. Does