Following ebuilds will need to be changed: jit/jit-1.1.6-r3.ebuild:RDEPEND=">=net-im/jabberd-1.4.3-r3" jud/jud-0.5.ebuild:DEPEND=">=net-im/jabberd-1.4.3" msn-transport/msn-transport-20040531-r1.ebuild:DEPEND=">=net-im/jabberd-1.4 msn-transport/msn-transport-20040531.ebuild:DEPEND=">=net-im/jabberd-1.4 ^^^ those ebuilds should have "|| ( net-im/jabberd net-im/jabberd2 )" Following ebuilds have to be changed too: mu-conference/mu-conference-0.6.0-r1.ebuild:DEPEND="=net-im/jabberd-1.4* mu-conference/mu-conference-0.6.0-r2.ebuild:DEPEND="=net-im/jabberd-1.4* yahoo-transport/yahoo-transport-2.3.0-r3.ebuild:DEPEND="=net-im/jabberd-1.4*" yahoo-transport/yahoo-transport-2.3.1-r1.ebuild:DEPEND="=net-im/jabberd-1.4* yahoo-transport/yahoo-transport-2.3.2.ebuild:DEPEND="=net-im/jabberd-1.4* ^^^ those ebuilds should have "net-im/jabberd" instead of =net-im/jabberd-1.4* Please fix them or give me a green light to do so.
net-im/jabberd2 is masked until it gets ~sparc and ~ppc. Masked also until I can make a proper blocks in net-im/jabberd.
net-im: can I make the changes mentioned in comment #0 after net-im/jabberd2 gets its keywords?
Gustavo: you're marked as <maintainer> for all those packages - can I make those changes? jabberd2 has proper keywords now.
I have jabberd-2.1.6 installed. I don't know how the "world" is maintained so I just want to make sure that after the jabberd2 ebuilds are unmasked for x86 will I have to unmerge it and merge again or will it work out of the box?
(In reply to comment #4) > I have jabberd-2.1.6 installed. I don't know how the "world" is maintained so I > just want to make sure that after the jabberd2 ebuilds are unmasked for x86 > will I have to unmerge it and merge again or will it work out of the box? Yes, you'll have to umerge net-im/jabberd and merge net-im/jabberd2. Config files will not be removed, so after those two commands it should continue to work.
I've made changes to following packages: * msn-transport * mu-conference * yahoo-transport jit and jud were removed.