On Sun, Jun 18, 2000 at 02:52:38PM -0600, Bdale Garbee wrote:
> copyright - upstream author, location, copyright, license
>
> README.Debian - anything non-obvious about this package on Debian,
> which would include any overall configuration
>
Bdale Garbee wrote:
> In the time when we didn't have as many well-known filenames in each package,
> the current policy may have made sense. I don't really think it does today.
FWIW, I agree with Bdale's message 100%. Note that the concept of a
README.Debian file was introduced about 3 years ago
> copyright - upstream author, location, copyright, license
>
> README.Debian - anything non-obvious about this package on Debian,
> which would include any overall configuration
> decisions, FAQ's, etc. A good example is in the
I've thought about this a bit, since Josip pointed the issue out to me on IRC.
Here is my take on it, as a long-timer...
I was never aware that policy required putting a summary of changes in the
copyright file, and I've never done it. I note that a couple packages I now
maintain contain such con
4 matches
Mail list logo
