El Diumenge, 2 de març de 2014, a les 21:32:58, Matthew Dawson va escriure:
On March 3, 2014 12:51:10 AM Albert Astals Cid wrote:
I wasn't following the discussion. Can anyone summarize how 4.x are
releases affected?
Thanks!
Albert
The kdnssd repository in the kdenetwork module
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
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
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
On Wednesday 26 February 2014 14:36:49 Nicolas Lécureuil wrote:
Le mercredi 26 février 2014 11:54:16 Alex Merry a écrit :
On 26/02/14 10:01, Alex Merry wrote:
Actually, having slept on it, my suggestion is:
- rename kdnssd to zeroconf-ioslave
- rename kdnssd-framework to kdnssd
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
On 01/03/14 09:57, David Faure wrote:
On Wednesday 26 February 2014 14:36:49 Nicolas Lécureuil wrote:
as there is already a kdnssd tarball for kde 4, i think this would be safer
to keep the -framework in the name.
I can't see how the name of the kde-sc-4 tarballs matter?
This is version 5
that
kdnssd stuff can disappear from there.
Actually, having slept on it, my suggestion is:
- rename kdnssd to zeroconf-ioslave
- rename kdnssd-framework to kdnssd
- merge the frameworks branch of zeroconf-ioslave into kio
BTW, I hope you've seen Matthieu Gallien patch around kdnssd? Would
On 26/02/14 10:01, Alex Merry wrote:
Actually, having slept on it, my suggestion is:
- rename kdnssd to zeroconf-ioslave
- rename kdnssd-framework to kdnssd
- merge the frameworks branch of zeroconf-ioslave into kio
I don't think the last part is necessarily a blocker, either (although
it's
Le mercredi 26 février 2014 11:54:16 Alex Merry a écrit :
On 26/02/14 10:01, Alex Merry wrote:
Actually, having slept on it, my suggestion is:
- rename kdnssd to zeroconf-ioslave
- rename kdnssd-framework to kdnssd
- merge the frameworks branch of zeroconf-ioslave into kio
I don't
On 02/27/2014 12:36 AM, Nicolas Lécureuil wrote:
Le mercredi 26 février 2014 11:54:16 Alex Merry a écrit :
On 26/02/14 10:01, Alex Merry wrote:
Actually, having slept on it, my suggestion is:
- rename kdnssd to zeroconf-ioslave
- rename kdnssd-framework to kdnssd
- merge the frameworks
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
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
13 matches
Mail list logo
