Summary: | net-analyzer/smokeping bundles perl-core/JSON-PP | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Peter Volkov (RETIRED) <pva> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | perl |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 356171 | ||
Attachments: |
Build log
move JSON-1 to /usr/share/smokeping |
Description
Diego Elio Pettenò (RETIRED)
![]() I am adding the perl-5.14.0 blocker because that version will install JSON::PP too. Diego smokeping uses JSON-1.x that we do not have in the tree http://bugs.gentoo.org/show_bug.cgi?id=260170#c2 . So until somebody ports smokeping to new JSON (actually only qooxdoo part uses it but looking at trunk upstream is not interested in upgrading this part) smokeping will just have blockers ... Blocker added. Fixed. That's not even barely fixed. It creates bug in other software because it doesn't install it in a _private_ directory, it does so in the _system perl directory_. (In reply to comment #3) > It creates bug in other software because it doesn't install it in a _private_ > directory, it does so in the _system perl directory_. Ok, I'll take a look. BTW, do you (or may be perl team) have pointers on documentation? I'm using this package and thus maintain, but I really have very sparse knowledge on perl build system... @perl, also I'd removed blocker as I don't see reasons for it. Nothing perl-5.14 is here. But that's up to you. Created attachment 265801 [details]
move JSON-1 to /usr/share/smokeping
- installs JSON-1 in PERL5SMOKEPING=/usr/share/smokeping/perl5
- adds `use lib '${PERL5SMOKEPING}';` to Qooxdoo::JSONRPC only
(^ untested, but i guess this is one way to do it? You should try it with
dev-perl/JSON-2.27 and ( dev-perl/JSON-2.510.0 and perl-core/JSON-PP ) )
- depends on dev-perl/Config-Grammar
*** Bug 358385 has been marked as a duplicate of this bug. *** Torsten, thank you very much for this job. Fixed. I think now it's ok to unmask Config-Grammar... |