Re: Alternative names in upstream changelogs

2000-05-02 Thread Steve Greenland
On 02-May-00, 01:40 (CDT), Joey Hess <[EMAIL PROTECTED]> wrote: > [w.r.t. preserving the names of upstream changelogs] > The default would become -k if something about preserving names was > added to policy. > > I don't think the name always has to be preserved, it seems that in some > cases ther

Re: Alternative names in upstream changelogs

2000-05-02 Thread Joey Hess
Steve Greenland wrote: > > Fine if you don't care about preserving the name. It can be important to > > preserve the name if some other document refers to CHANGES, or if > > you think the upstream author might refer to the CHANGES sometime or > > be annoyed that you renamed it. > > > > I don't thi

Re: Alternative names in upstream changelogs

2000-05-01 Thread Steve Greenland
On 01-May-00, 00:38 (CDT), Joey Hess <[EMAIL PROTECTED]> wrote: > Steve Greenland wrote: > > Debian policy requires that the upstream changelog be accessible as > > /usr/share/doc//changelog.gz. Some (many?) authors use an > > alternative name for their changelog, with "CHANGES" seeming to be the

Re: Alternative names in upstream changelogs

2000-05-01 Thread Joey Hess
Steve Greenland wrote: > Debian policy requires that the upstream changelog be accessible as > /usr/share/doc//changelog.gz. Some (many?) authors use an > alternative name for their changelog, with "CHANGES" seeming to be the > most popular. What is the appropriate thing to do? Note that I conside

Alternative names in upstream changelogs

2000-05-01 Thread Steve Greenland
Debian policy requires that the upstream changelog be accessible as /usr/share/doc//changelog.gz. Some (many?) authors use an alternative name for their changelog, with "CHANGES" seeming to be the most popular. What is the appropriate thing to do? 1. Copy to changelog and compress? 2a. Copy as CH