kio_man

Martin Koller kollix at aon.at
Fri Aug 24 15:59:56 BST 2018


On Freitag, 24. August 2018 14:39:45 CEST Luigi Toscano wrote:
> Martin Koller ha scritto:
> > Hi,
> > 
> > I'm just checking for https://bugs.kde.org/show_bug.cgi?id=321074
> > why my fix done in 2015 does not work in 18.08, and I discovered, that
> > the commit done at this time into the kde-runtime repo is not in the kio_man source
> > of the new repo in kio-extras.
> > 
> > Can someone help me to explain how/when the repo was moved and for which
> > commits I need to check if missing in the new one ?
> > 
> 
> kde-runtime does not exist anymore: it was an heterogeneous mix of stuff which 
> complemented kdelibs 4.x, and basically required by any kdelibs 4.x 
> application to run.
> 
> Everything that was there ended in various places (independent repositories, 
> or Plasma, depending on the content).
> The process was mostly the same for the frameworks branch of kdelibs and the 
> frameworks branch of kde-runtime: in both cases, the content was moved (with 
> history, or with grafts to the previous history) somewhere else.
> 
> You can compare the different histories:
> https://cgit.kde.org/kio-extras.git/log/man
> https://cgit.kde.org/kde-runtime.git/log/kioslave/man
> 
> It looks like all 6 changes that you did in 2015 (which was way after the 
> split) are not in kio-extras.

That's bad. I'll manually bring them over to kio-extras

> Probably a direct cherry-pick is not going to work, and some commits need 
> changes.

> For example, I would not apply blindly "Do not use KEncodingProber - 
> it gives false results; Try dirname or UTF8" for two good reasons 
> (KEcondingProber should be fixed, and the improvements in Qt5).

First step is to bring my commits from the old repo to the new one - with
the least changes.
The first of them shows that the problem with KEcondingProber still exists.
What improvements in Qt5 are you thinking about which would help here ?

> Also "Adding 
> .St macro from groff_mdoc package (Standards Names)" should consider that the 
> gperf file is generated dynamically now.

yeah, as said, I'll manually check each commit ...

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\                        - against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at






More information about the kfm-devel mailing list