On Wed, 2 Jan 2002, John Powell wrote:
> Sounds like the best approach is to submit to the author (Mitel) in > the form of modified RPMs and hope for adoption. I have an idea > already on making them optional, move most directory info (everything > except first and last names) to a separate panel. I will do that once > 5.1 goes gold so I know that it is on the latest codebase. Why wait? Since you will be making your changes as a patch to the existing code, due to the wonders of Larry Wall's patch utility (yes, the same Larry Wall), it's likely to be very simple to apply the same patch to any later version of the code (e.g., the version from 5.1 gold). > I do not like the idea of making them available separately (except for > testing and feedback) as I would think even a blade update, and almost > definitely a system upgrade, will overwrite the modified panels and > scripts. Yes, it's true that any Mitel update will overwrite your changes. But I don't see that as any reason not to make the code generally available. It's not as though you would force anyone to use your version of the code. Remember too the nature of GPL software. Once you make changes available for testing and feedback, the genie is out of the bottle - you may not make the code generally available, but anyone else may. -- Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Group http://www.e-smith.com/ Mitel Networks Corporation http://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
