#8837 NORM xs-0.5: replace ejabberd with ejabberd-xs and finish off ejabberd packaging

[Zarro Boogs per Child]

#8837: replace ejabberd with ejabberd-xs and finish off ejabberd packaging
-----------------------------+----------------------------------------------
 Reporter:  martin.langhoff  |         Owner:  douglas      
     Type:  task             |        Status:  new          
 Priority:  normal           |     Milestone:  xs-0.5       
Component:  school server    |       Version:  not specified
 Keywords:                   |   Next_action:  never set    
 Verified:  0                |     Blockedby:               
 Blocking:                   |  
-----------------------------+----------------------------------------------
 And set conflicts and replaces appropriately, as Seth suggests in the
 email below.

 Also finish off

 - ensuring that xs-config uses the new sysconfig/ejabberd file and
 separate config
 - checking what the story is with the PEM file


 ---------- Forwarded message ----------
 From: seth vidal <skvidal at fedoraproject.org>
 Date: Wed, Oct 15, 2008 at 12:52 AM
 Subject: Re: [Server-devel] Tying yum to a package "stream"?
 To: Discussion of Fedora build system <fedora-buildsys-list at redhat.com>
 Cc: XS Devel <server-devel at lists.laptop.org>


 On Tue, 2008-10-14 at 18:49 +1300, Martin Langhoff wrote:
 > On Tue, Oct 14, 2008 at 6:16 PM, Mike McLean <mikem at redhat.com> wrote:
 > > If you go this route, I think what you want is obsoletes. Obsoletes
 says
 > > "this packages replaces this one." Conflicts says "this package cannot
 be
 > > installed at the same time as this other one."
 >
 > Does 'obsoletes' also mean "this package cannot be installed at the
 > same time as this other one."? Because things *will* go wrong if
 > someone installs moodle and moodle-xs :-/

 You can obsolete and conflict

 Obsoletes: pkgname=ver.rel
 Conflicts: pkgname=ver.rel

 -sv

-- 
Ticket URL: <http://dev.laptop.org/ticket/8837>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system