Jaime, > > Blades can be open-source, closed-source, proprietary, whatever. They can > > be licensed under the GPL or any other license. They can be completely > > free or there can be a charge for them. > > Sorry, I didn't explained myself. I was talking about the blade "system" > not the blade itself. Can it be made to run on a ESGS 4.1.2 system? Can it be > dettached from Mitel systems? No, the mechanism to download the blade from our network operations center only runs on SME Server V5 or later.
> We didn't intend this for "supported" contrib or updates. There are plenty > of unsupported contribs around that I might like to include even if Mitel > doesn't support it (for example our own monitor system). Most of them play > nice with ESGS once you know the little needed tricks. Sorry, *I* wasn't being clear. Our blades architecture allows for both "Supported" blades where Mitel will provide support and "Unsupported" blades where we will provide no direct support. Both can go through our delivery mechanism. > I don't expected support from this, just an easy way of sending my future > clients updates, custom work, whatever. Understood. > I'm sorry Dan but I don't agree here. The "blades concept" was one of the > main point of SME server (the other one was service link). As I see it is a > wonderfull toy BUT the only ones playing with it are you. I didn't expect > Mitel to support those blades I just expected them to tell everybody how to > play too. I'm with you. We understand that. We know. Believe me, it's something we want to change. We know that. > I'm not really trying to replace the blade concept. I'm just giving an > alternative. Surely most people will use the standar blades but some people > might like to have "more freedom". As the upd file is so easy to make I don't > consider this a double effort (I bet you a blade is not particulary easy to > make or you wouldn't have delayed so much). Yes, I understand. I don't have any issue at all with you working on this. > It took me an hour to explain how to make an upd file and make the > announcement. Sure it needs some polish (thats what this list is for BTW) and > I really beleive they can both coexist, one for "Oficial" updates the other > for "custom" updates. Yep. > > In the meantime, Charlie had a previous post that gave some information: > > > > http://www.mail-archive.com/[email protected]/msg06971.html > > > > Essentially, build a contrib RPM, build a wrapper RPM as Charlie mentions, > > and drop us a note. I'll be willing to be a contact for potential blades. > > What is a RPM wrapper? :'( As I understand Charlie's note, he is just talking about a second RPM that specifies what other RPMs are required and also executes any post-install scripts, etc. Regards, Dan -- Dan York, Product Line Manager, SME Server and ServiceLink Mitel Networks Corporation [EMAIL PROTECTED] Ph: +1-613-751-4401 Cell: +1-613-263-4312 Fax: +1-613-564-7739 150 Metcalfe Street, Suite 1500, Ottawa,ON K2P 1P1 Canada http://www.mitel.com/sme/ and http://www.e-smith.com/ -- 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
