Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 858800 - dev-util/kio-perldoc should be kde-misc/kio-perldoc
Summary: dev-util/kio-perldoc should be kde-misc/kio-perldoc
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-18 13:20 UTC by David Haller
Modified: 2024-06-24 19:21 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Haller 2022-07-18 13:20:06 UTC
All other /kio-* besides net-misc/kio-zeroconf and kde-apps/kio-extras are in kde-misc/, so kio-perldoc should be there too (and as it's being moved anyway)...
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-07-18 13:25:36 UTC
I think we're trying to avoid bloating kde-*/* unless necessary. Docs make sense for dev-util/?
Comment 2 Andreas Sturmlechner gentoo-dev 2022-07-18 14:35:52 UTC
I'd argue these categories (apart from Frameworks/Plasma) are rather obsolete. Probably 40% of packages are misplaced applications outside of KDE Applications/Gear where it was easier to throw it in there rather than think of a proper category, and for the remaining packages it is questionable to maintain a separate category. Then at least two old kio-* will probably be dead with the need to port to Qt6 and no upstream maintainer for a long time.
Comment 3 David Haller 2022-07-18 14:52:13 UTC
Well, kio-* are almost all in kde-misc/ besides the (IMHO misplaced) kde-apps/kio-extras (which has no app, just kio-plugins and stuff and should be in kde-misc/ too ;) and the kde-frameworks/kio. There's net-misc/kio-zeroconf and app-arch/kio_p7zip::bgo-overlay. Anyway, if it's to be outside of kde-*, it should be in app-text/ like e.g. pinfo or tkman and not in dev-util/. And then (longterm), the other kio-plugins should be moved to better categories too, e.g. kde-misc/kio-fuse -> sys-fs/kio-fuse[1] and similiar. But while we're moving stuff around, I thought kio-perldoc belongs in kde-misc/ (or app-text/).
YMMV.

[1] but there's dev-perl/Fuse, dev-python/fuse-python too ... one could argue for moving it to dev-perl/kio-perldoc as well... makes more sense than dev-util/ IMHO.
Comment 4 Andreas Sturmlechner gentoo-dev 2022-07-18 15:21:02 UTC
(In reply to David Haller from comment #3)
> Well, kio-* are almost all in kde-misc/ besides the (IMHO misplaced)
> kde-apps/kio-extras (which has no app, just kio-plugins and stuff and should
> be in kde-misc/ too ;) and the kde-frameworks/kio.
kio-extras placement is historical, and it will eventually be moved somewhere else too. kde-frameworks/kio placement makes sense as a KDE Frameworks module.

> Anyway, if it's to be outside of kde-*, it should be in app-text/ like e.g. pinfo or tkman and not in dev-util/.
Would fit as well, but dev-util has precedence as well with e.g. gtk-doc, gnome-devel-docs.

> And then (longterm), the other kio-plugins should be
> moved to better categories too, e.g. kde-misc/kio-fuse -> sys-fs/kio-fuse[1]
> and similiar. But while we're moving stuff around, I thought kio-perldoc
> belongs in kde-misc/ (or app-text/).
Sure, the key term here is longterm. I am changing to new category as I go, disregarding short term orderliness, because we don't want to make needless pkgmoves really.

> [1] but there's dev-perl/Fuse, dev-python/fuse-python too ... one could
> argue for moving it to dev-perl/kio-perldoc as well... makes more sense than
> dev-util/ IMHO.
Those categores are for packages fundamentally written in perl/python, which kio-perldoc is to some extent as well, but in the end it is just a utility for the kio worker module.
Comment 5 David Haller 2022-07-23 18:27:57 UTC
(In reply to Andreas Sturmlechner from comment #4)
> (In reply to David Haller from comment #3)
> > Well, kio-* are almost all in kde-misc/ besides the (IMHO misplaced)
> > kde-apps/kio-extras (which has no app, just kio-plugins and stuff and should
> > be in kde-misc/ too ;) and the kde-frameworks/kio.
> kio-extras placement is historical, and it will eventually be moved
> somewhere else too.

I thought as much. Judging from it's list of kio-plugins, it should actually be
named kio-base-plugins or some-such (with its {man,info,archive,...}.so plugins)
and IMO be placed into kde-misc/ (or maybe even kde-frameworks/)...

> kde-frameworks/kio placement makes sense as a KDE
> Frameworks module.

That one was just mentioned for completeness of kio-stuff outside of kde-misc/ ;)

> > Anyway, if it's to be outside of kde-*, it should be in app-text/ like e.g.
> > pinfo or tkman and not in dev-util/.
> Would fit as well, but dev-util has precedence as well with e.g. gtk-doc,
> gnome-devel-docs.

Are gtk-doc and gnome-devel-docs apps for the enduser to display documentation?
AFAIK no. kio-perldoc though is (AFAIK, maybe indirectly, but transparent to the
user). I just think it does not belong into dev-util/. Compare the file lists:

kio-perldoc: kf5/kio/perldoc.so, /usr/share/kio_perldoc/pod2html.pl -> nothing a
developer 

> > And then (longterm), the other kio-plugins should be
> > moved to better categories too, e.g. kde-misc/kio-fuse -> sys-fs/kio-fuse[1]
> > and similiar. But while we're moving stuff around, I thought kio-perldoc
> > belongs in kde-misc/ (or app-text/).
> Sure, the key term here is longterm. I am changing to new category as I go,
> disregarding short term orderliness, because we don't want to make needless
> pkgmoves really.
> 
> > [1] but there's dev-perl/Fuse, dev-python/fuse-python too ... one could
> > argue for moving it to dev-perl/kio-perldoc as well... makes more sense than
> > dev-util/ IMHO.
> Those categores are for packages fundamentally written in perl/python, which
> kio-perldoc is to some extent as well, but in the end it is just a utility
> for the kio worker module.
Comment 6 David Haller 2022-07-23 19:20:28 UTC
(In reply to Andreas Sturmlechner from comment #4)
> (In reply to David Haller from comment #3)
> > Well, kio-* are almost all in kde-misc/ besides the (IMHO misplaced)
> > kde-apps/kio-extras (which has no app, just kio-plugins and stuff and should
> > be in kde-misc/ too ;) and the kde-frameworks/kio.
> kio-extras placement is historical, and it will eventually be moved
> somewhere else too.

I thought as much. Actually, looking at the plugins and comparing to those
contained in kde-frameworks/kio again, I think it _should_ be
kde-misc/kio-extras.

> kde-frameworks/kio placement makes sense as a KDE
> Frameworks module.

That one was just mentioned for completeness of kio-stuff outside of kde-misc/ ;)

> > Anyway, if it's to be outside of kde-*, it should be in app-text/ like e.g.
> > pinfo or tkman and not in dev-util/.
> Would fit as well, but dev-util has precedence as well with e.g. gtk-doc,
> gnome-devel-docs.

Are gtk-doc and gnome-devel-docs apps for the enduser to display documentation?
AFAIK no. kio-perldoc though is (AFAIK, maybe indirectly, but transparent to the
user). I just think it does not belong into dev-util/. Compare the file lists.

kio-perldoc: kf5/kio/perldoc.so, /usr/share/kio_perldoc/pod2html.pl -> nothing a
  developer needs to use, but stuff a *user* needs to display perldoc documentation
  (albeit: the user probably will be a perl developer in some way or other at that
  time ;) Note: kio-perldoc does _NOT_ contain any perl documentation itself besides
  what is inside pod2html.pl
  => KDE (specific) app/plugin to *display* documentation => belongs into kde-misc/
     or some other kde-*/ category, but IMHO clearly not into dev-util/.

gtk-doc: /usr/bin/gtkdoc-*, /usr/share/gtk-doc/python/gtkdoc/* -> stuff a developer
  or packager uses to *convert* or *generate* documentation
  => tools for devs/packagers to create documentation => clearly belongs into dev-util/

gnome-devel-docs: only contains gnome documentation for developers, no app to 
  display the "*.page" xml-files it contains. Where then, is the "util" in that
  package?
  => clearly just documentation (contents) for (gnome-)devs => dev-util/ is ok,
    but only for lack of a better category, as app-doc/ does not really make sense
    either. I'd prefer some gnome- subcategory, but that might be just me disliking
    gnome ;)

You see the differences? But nice, that you've brought up these completely different
package examples.

I see kio-perldoc like a html- or pdfviewer-plugin for whatever app, like something
you usually get with a 'pdf' useflag in doc-viewing apps like okular.

> > And then (longterm), the other kio-plugins should be

(... i.e. unless we just keep them in kde-misc/ ...)

> > moved to better categories too, e.g. kde-misc/kio-fuse -> sys-fs/kio-fuse[1]
> > and similiar. But while we're moving stuff around, I thought kio-perldoc
> > belongs in kde-misc/ (or app-text/).
> Sure, the key term here is longterm. I am changing to new category as I go,
> disregarding short term orderliness, because we don't want to make needless
> pkgmoves really.

Exactly. 

Regarding kio-perldoc: it's being moved, that's why I piped up before this
move is "stabilized". Sorry for not noticing anything earlier. And why not move
it to a fitting category now as it's being moved anyway instead of moving it
(or probably not) some time later. And I think kde-misc/ is just right, as it's
KDE specific stuff that only some other KDE app can use (in this case to display
perldocs). And kde-misc/ is where most other kio plugins are.
 
> > [1] but there's dev-perl/Fuse, dev-python/fuse-python too ... one could
> > argue for moving it to dev-perl/kio-perldoc as well... makes more sense than
> > dev-util/ IMHO.
> Those categores are for packages fundamentally written in perl/python, which
> kio-perldoc is to some extent as well, but in the end it is just a utility
> for the kio worker module.

That's exactly why I think it belongs in kde-misc/.
Comment 7 David Haller 2022-07-23 19:22:56 UTC
Please ignore due to "mid-air collision"