Adrian Bunk <[EMAIL PROTECTED]> writes: > It's different when the Debian maintainer is also upstream. It is argued > that then there's only one `debianization'. That's all right but please > consider the following cases before making your package Debian native: > - Do you want to release a new upstream version to fix a missing build > dependency?
And further- What if your program outlives your interest in it? i.e. what if someone else takes it over upstream eventually, and they're not a Debian developer? I tend to think that in many cases, preserving the upstream/Debian distinction is wise, even if not totally necessary ATM. -- Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
