Re: [RP] Re: obsolete build-depends in CVS debian directory

[Bernhard R. Link]

* Graham Wilson <address@hidden> [060117 20:27]:
> Debian best practices dictate that the debian/ directory not be kept in
> upstream's source management system or in upstream's release tarballs.

Best practise is only to not have them in the release tarball.

> This way the Debian maintainer doesn't have to keep upstream's CVS in
> sync with his local copy everytime he makes an new debian release.

This could be a problem with other revision control systems.
Cvs however is extremly local, just do a checkout and remove
or rename the debian directory. (Though removing is possibly better, as
one does not have to look at it then through accident), 
and add your debian directory. (I'm doing so all the time with my local
version of ratpoison Debian packages).

> Additionally, sometimes Debian maintainer's need to apply local patches
> to the source that are not appropriate for upstream.

That's not only special for the debian/ dir but for the whole source
package. (And there is no real problem for that. The only proble is that
the Debian source format does not allow removing files, and the
existance of files in that directory can have a meaning when using
special files).

Hochachtungsvoll,
        Bernhard R. Link