KDNSSD merge

Albert Astals Cid aacid at kde.org
Sun Mar 2 23:51:10 UTC 2014


El Diumenge, 2 de març de 2014, a les 11:39:15, David Faure va escriure:
> On Saturday 01 March 2014 10:27:08 Alex Merry wrote:
> > On 01/03/14 09:55, David Faure wrote:
> > > On Tuesday 25 February 2014 20:37:28 Alex Merry wrote:
> > >> I've had a look at the kdnssd repositoy, and it contains two related
> > >> bits of code: the zeroconf ioslave and a kded/KDirWatch module to
> > >> notify
> > >> KIO about changes to available services.
> > >> 
> > >> These two obviously belong together; the question is where?  They can
> > >> go
> > >> in kdnssd-framework, making it depend on KIO, or they can go in KIO,
> > >> making it (optionally) depend on KDNSSD.
> > > 
> > > I don't like the idea of adding yet another dependency to KIO.
> > > 
> > > How about we put the kioslave which depends on kio+kdnssd into some
> > > tier4
> > > framework? After all it's not API, it's just some integration plugin,
> > > which is exactly what defines tier4.
> > 
> > Do we want a kioslaves framework (somewhat similar to the kimageplugins
> > framework)?
> 
> I think that would make sense -- we have a whole bunch of kioslaves in
> kde-runtime that we don't know where to put (lots of "??" in the
> New_Runtime_Organization epic).
> 
> I don't think we want all of these into the kio framework, that would make
> it depend on libsmbclient, libssh and all sorts of other libs.
> 
> Kevin, do you agree on a kioslaves.git repo, tier4?
> 
> > >> Also, what happens to the old repo, which is part of kdenetwork, and
> > >> hence KDE SC?
> > > 
> > > Nothing? Just like kdelibs.
> > 
> > Well, except we don't have a framework called "kdelibs", so there's no
> > name clash.  My question was: if we rename kdnssd-framework to kdnssd,
> > what happens to the existing kdnssd framework.
> 
> Ah, now I see.
> 
> > I suggested in another email that we also rename that.
> 
> ... to zeroconf-ioslave, right. That would be OK with me, but indeed this
> requires approval from release-team since it affects 4.x releases.

I wasn't following the discussion. Can anyone summarize how 4.x are releases 
affected?

Thanks!

Albert


More information about the Kde-frameworks-devel mailing list