> Sure, but the same could be said for any upstream file, not just the > makefiles. The question is just where we draw the line, i.e., what do > we require be removed and what do we let the project team keep.
In an earlier email, I stated my personal opinions for where to draw the line. For the record, I certainly think there are cases where it makes sense to keep unreferenced upstream files. > I had thought that we had more upstream makefiles than we do. But as I > mentioned earlier, the only ones I know of are tcpd and grub. So I can > see arguing for a precedent that upstream makefiles must be removed. In > that case, we really need to write this down, so that all projects are > held to the same standard. Agreed. AFAIK, the unreferenced file policy in general is not written down (other than the original heads-up I sent out back in 2001), but rather has been passed down from one gatekeeping team to the next. Both a manpage for findunref and a written policy are overdue. I'd be happy to work with the gatestaff (or whoever else needs to be involved) on this as a background task. -- meem
