Søren Boll Overgaard wrote: > Essentially, what it boils down to is this: Would it be prudent to include two > separate versions of pan in etch (perhaps named pan and pan2)? This should be avoided where possible; if they share a common code base it's quite likely that discovered security problems need to be fixed in both source packages. Cheers, Moritz