source packages and extensible apps

I'm working on packaging the Berkeley NS (network simulator) code. This is an extensible app, in the sense that users modify and add to the source code to add their own features. Two questions: - How should such a program be packaged? As a source package only or as both a source and a binary pa

libotcl1 package completed

I've finally packaged up the shared and static versions of the otcl libraries. Otcl allows embedded objects in tcl and is used by a number of interesting applications. I've only compiled them against libc5 but will upgrade them to libc6 soon, I hope. Testing is encouraged. Take a look at: ht

Example library, please

Hi, I'm trying to build packages for a library and running into a number of problems. I've build a package for a regular executable by following the instructions in the Debian Packaging Manual. However, I haven't found a step-by-step dicussion of how to build a library. I was hoping someone on

ipgrab package

I've built a package for ipgrab 0.4a1, a tcpdump-like utility that prints out extensive Ethernet/IP/TCP/UDP/ARP header info. It was built against libc5 so I don't know how useful it will be for now. I'll upload it as soon as I get an account on debian.org. If anybody wants to test it, go to