[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-frameworks-devel
Subject: Re: Kioslave repos
From: Aleix Pol <aleixpol () kde ! org>
Date: 2014-04-27 17:40:17
Message-ID: CACcA1Rr2ma2K8x2Bvco6qhNL8ciituU03tjRajcn0sS0-VcJ-Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Sun, Apr 27, 2014 at 3:39 PM, David Faure <faure@kde.org> wrote:
> On Tuesday 08 April 2014 06:02:33 =C3=80lex Fiestas wrote:
> > On Monday 07 April 2014 23:27:33 Alex Merry wrote:
> > > Aleix wanted a separate thread for this, so here it is.
> > >
> > > The current runtime splitting plan says that ioslaves should be in
> three
> > > places: core ones (file, http, etc) in kio, other useful ones (archiv=
e,
> > > bookmarks, etc) in "kioslaves", and curiosities (cgi, finger) in
> > > kioslave-extra.
> > >
> > > In my view, this is too many repos (and I apologise for not bringing =
it
> > > up sooner, but the last I'd seen on the list, only one repo outside k=
io
> > > was being suggested, and I hadn't realised the plan had changed).
> > >
> > > Moving things between repos is a *pain*, and I think Ben and Albert
> have
> > > a point about being over-eager to split things up. In this case, I
> > > think we should just have core things in kio, and everything else in
> > > kioslaves (or call it kio-extra-slaves, or whatever). Everything in
> that
> > > package should be optional, and distros can split it up if they reall=
y
> > > want, but I don't think we should split it.
> >
> > The reason for the split is that they are not used, not maintained and
> they
> > are not of general interest. Few examples:
> >
> > kiosalves of interest:
> > sftp
> > fish
> > smb
> > ...
> > kioslaves not of interest:
> > settings (allows you to use dolphin/konqueror as systemsettings)
> > cgi (allows you to execute cgi without having a web server)
> > finger
> >
> > I personally do not want to have those not of interest or unmaintained
> > kiosalves around, I do not want to maintain them, I do not want distros
> to
> > ship them by default (which will happen for those distros that will
> pacakge
> > the entire repository) etc.
> >
> > Maybe we can move them to unmaintain (there is such place in our git
> repos I
> > think) or something like that, but I really think that kio_cgi does no=
t
> > belong near smb.
>
> Here's my take on this topic:
>
> * kill settings, cgi and finger
> * move kio_desktop to workspace
> * put the rest in a kio-extras repo (that part is done, I see)
> * place that repo in kde/ or kde/<something> in the projects.kde.org
> hierarchy, so that it gets released with the KDE Applications, NOT with t=
he
> workspace product. Support for kio_fish/kio_sftp on Windows or Gnome
> desktops
> is one of the major selling points of Dolphin there, this is "apps", not
> "workspace".
>
> (I can help with the last task, moving on p.k.o, if everyone agrees)
>
> --
> David Faure, faure@kde.org, http://www.davidfaure.fr
> Working on KDE Frameworks 5
>
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
Makes sense to me. +1
Aleix
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Apr 27, 2014 \
at 3:39 PM, David Faure <span dir="ltr"><<a href="mailto:faure@kde.org" \
target="_blank">faure@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Tuesday 08 April 2014 06:02:33 Àlex Fiestas \
wrote:<br> > On Monday 07 April 2014 23:27:33 Alex Merry wrote:<br>
> > Aleix wanted a separate thread for this, so here it is.<br>
> ><br>
> > The current runtime splitting plan says that ioslaves should be in \
three<br> > > places: core ones (file, http, etc) in kio, other useful ones \
(archive,<br> > > bookmarks, etc) in "kioslaves", and curiosities \
(cgi, finger) in<br> > > kioslave-extra.<br>
> ><br>
> > In my view, this is too many repos (and I apologise for not bringing it<br>
> > up sooner, but the last I'd seen on the list, only one repo outside \
kio<br> > > was being suggested, and I hadn't realised the plan had \
changed).<br> > ><br>
> > Moving things between repos is a *pain*, and I think Ben and Albert \
have<br> > > a point about being over-eager to split things up. In this case, \
I<br> > > think we should just have core things in kio, and everything else \
in<br> > > kioslaves (or call it kio-extra-slaves, or whatever). Everything in \
that<br> > > package should be optional, and distros can split it up if they \
really<br> > > want, but I don't think we should split it.<br>
><br>
> The reason for the split is that they are not used, not maintained and they<br>
> are not of general interest. Few examples:<br>
><br>
> kiosalves of interest:<br>
> sftp<br>
> fish<br>
> smb<br>
> ...<br>
> kioslaves not of interest:<br>
> settings (allows you to use dolphin/konqueror as systemsettings)<br>
> cgi (allows you to execute cgi without having a web server)<br>
> finger<br>
><br>
> I personally do not want to have those not of interest or unmaintained<br>
> kiosalves around, I do not want to maintain them, I do not want distros to<br>
> ship them by default (which will happen for those distros that will pacakge<br>
> the entire repository) etc.<br>
><br>
> Maybe we can move them to unmaintain (there is such place in our git repos I<br>
> think) or something like that, but I really think that kio_cgi does not<br>
> belong near smb.<br>
<br>
</div></div>Here's my take on this topic:<br>
<br>
* kill settings, cgi and finger<br>
* move kio_desktop to workspace<br>
* put the rest in a kio-extras repo (that part is done, I see)<br>
* place that repo in kde/ or kde/<something> in the <a \
href="http://projects.kde.org" target="_blank">projects.kde.org</a><br> hierarchy, so \
that it gets released with the KDE Applications, NOT with the<br> workspace product. \
Support for kio_fish/kio_sftp on Windows or Gnome desktops<br> is one of the major \
selling points of Dolphin there, this is "apps", not<br> \
"workspace".<br> <br>
(I can help with the last task, moving on p.k.o, if everyone agrees)<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
David Faure, <a href="mailto:faure@kde.org">faure@kde.org</a>, <a \
href="http://www.davidfaure.fr" target="_blank">http://www.davidfaure.fr</a><br> \
Working on KDE Frameworks 5<br> </font></span><div class="HOEnZb"><div \
class="h5"><br> _______________________________________________<br>
Kde-frameworks-devel mailing list<br>
<a href="mailto:Kde-frameworks-devel@kde.org">Kde-frameworks-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-frameworks-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-frameworks-devel</a><br> \
</div></div></blockquote></div><br></div><div class="gmail_extra">Makes sense to me. \
+1</div><div class="gmail_extra"><br></div><div class="gmail_extra">Aleix</div></div>
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic