Bug 917256

Summary: Inkscape dependencies (esp. perl ones) should be revisited
Product: [Fedora] Fedora Reporter: Cedric Sodhi <manday>
Component: inkscapeAssignee: Gwyn Ciesla <gwync>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: duffy, gwync, lkundrak
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 23:04:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
`equery g inkscape` on Gentoo x64 no-multilib Profile
none
`equery g inkscape` on Gentoo x64 no-multilib Profile none

Description Cedric Sodhi 2013-03-02 12:07:27 UTC 
Although Gentoo is not in any sort of a way a reference for correct dependencies, I attach the output of "equery g inkscape" which lists *all*, build- and runtime dependencies for Inkscape for the most functional setup.

Inkscape on F18 currently depends on exotic packages like the complete Perl-HTTP-Daemon suite.

Inkscape comes with 3 tiny perl scripts for user convenience (text2svg). Two points to note here:

None of those perl scripts depends on anything like a HTTP-Server.

If the dependencies get so blown out of proportions, owing to just a tiny perl script, it would be reasonable to split those out (given they are merely pluggable scripts) into a separate rpm "inkscape-tiny-script-which-will-pull-in-every-perl-package-on-the-planet.rpm" or similar.

Primary concern of this bug is the fact, that the dependency is wrong at least with the HTTP-Server part and possibly with other parts, too.
Comment 1 Cedric Sodhi 2013-03-02 12:09:19 UTC 
Created attachment 704471 [details]
`equery g inkscape` on Gentoo x64 no-multilib Profile
Comment 2 Cedric Sodhi 2013-03-02 12:11:18 UTC 
Created attachment 704473 [details]
`equery g inkscape` on Gentoo x64 no-multilib Profile
Comment 3 Gwyn Ciesla 2013-03-13 17:57:28 UTC 
The problem with doing that, though, is that in order for the inkscape binary to be able to use any Perl plugins, it must be linked against Perl, and will then pull in a large chunk of Perl packages.  Simply splitting the Perl files into a subpackage won't do anything to reduce the dependencies, unless we disable Perl plugin usage altogether, which I won't do while upstream continutes to ship Perl plugins, because users might be relying on them.  If upstream, in a subsequent release, removes all Perl plugins, I'll be happy to disable Perl support.
Comment 4 Cedric Sodhi 2013-03-13 18:30:02 UTC 
Your response adresses the problem of perl as a whole. However, could you please comment on what is another major concern in itsself, namely the whole HTTP-Server story?
Comment 5 Gwyn Ciesla 2013-03-13 18:58:46 UTC 
It looks like perl-HTTP-Daemon is needed by perl-libwww-perl, which is needed by perl-XML-DOM, needed by perl-XML-XQL, needed by SpSVG.pm.  Inkscape.pm doesn't seem to pull in much, the 4 .pl files pull in more.
Comment 6 Cedric Sodhi 2013-03-13 20:33:13 UTC 
This must either be a bug in the perl deps then or idiotic by design (to require a HTTP Server in order to parse XML).

You said that splitting the Perl files out wouldn't reduce that? If Inkscape only has to be compiled against perl (which, understandably, you don't want to change as long as upstream ships it so), wouldn't that at least relieve us of the HTTP Suite?
Comment 7 Gwyn Ciesla 2013-03-19 13:22:24 UTC 
My Perl knowledge isn't sufficient to determine whether the deps all the way down the chain are correct.  From what I see in the Inkscape code, the deps are correct at the Inkscape level, and from a disk space perspective, the savings gained from splitting out the perl files is minimal, since the Inkscape binary will pull in the bulk of the core perl anyway.
Comment 8 Fedora End Of Life 2013-12-21 15:24:56 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 9 Fedora End Of Life 2014-02-05 23:04:44 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.