[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

source packages that aren't

Is it (a) always, (b) sometimes or (c) never a bug for a source
package to contain, not the unpacked source, but another tarball,
which must be unpacked before one can do anything useful with the

shadow-20000902 is one example of such a package; I've run into others
in the past.

What is the point of this sort of arrangement?  It seems strange,
given that there is already a mechanism for separating the debian
patches from the upstream source.


Reply to: