Just imho: I'm not sure that I would like to update sipx using gui. For me command line is more suitable. I'm not sure that it's worth having 'update' button in gui, because when somebody types "make install" or "yum update" it's more likely that he understands what he's doing, in comparison to the user, who just clicks "update" button... Anyway if there will be a possibility to update sipx through gui, it will be a king of front end for yum, rpm, or other package managers on other platforms. And my idea was just to give administrator more understanding and control on what is happening...
Rgds, Nikolay. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sipx-dev- > [EMAIL PROTECTED] On Behalf Of Scott Lawrence > Sent: Friday, November 07, 2008 11:51 PM > To: Damian Krzeminski > Cc: [EMAIL PROTECTED] > Subject: Re: [sipX-dev] Software update UI feedback > > > On Fri, 2008-11-07 at 09:06 -0500, Damian Krzeminski wrote: > > Nikolay Kondratyev wrote: > > > Joe, > > > > > > Just an idea: it would be useful to be able to view/configure the > repository > > > that is being used for sipx sw update... > > > > What Joe is writing is not a front end for yum. There are several nice > > tools for that. What we are trying to achieve is to update the system > that > > has all necessary repositories configured already. > > > > In what cases you are changing the repositories? > > > > I am not against adding more capabilities after we have basic > functionality > > in place. I am just not so crazy about adding features just because some > > other tools have them. I'd rather support most common scenario in the > best > > possible way than support all scenarios in a poor way. > > I agree with Damian on this one, at least for now. > > I think that the way we'll end up supporting this is to make an rpm > whose only content is the repository definition for sipXecs updates, and > have that rpm declare a symbol that the sipXecs will depend on. That > way if someone wants to change what repository they update from, they'll > install the alternate rpm with that same symbol from the other > repository. > > None of that requires any change in the gui, which I'd like to keep as > simple (and non-scary) as possible, and incidentally not tie to yum > (since in other distros we may want the backend to be some other package > manager). > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
