Hi Chris, On 3/23/06, Chris Gianelloni <[EMAIL PROTECTED]> wrote: > If some random developer goes out there and creates his own fork of > catalyst in his overlay, I sure don't want to receive a *single* bug on > it. Ever.
Your nightmare scenario seems unavoidable. Enabling per-overlay bug tracking doesn't stop users posting bugs in bugzilla. It just causes confusion for users, because they're not sure where to go. Normally, it's not a problem - because the overlay contributors are normally the owners of the real package. A hostile fork of Catalyst is very much a special case. What we could do is say that overlays are for package trees only; ie they are not general-purpose repositories for holding source trees. That would ensure that your nightmare scenario is even less likely to happen, and that if it does, it's through no fault of the overlays project :) Best regards, Stu -- [email protected] mailing list
