Should use the system copy.
Why should it? Intended behavior, as per the YAML::Syck documentation: "The current implementation bundles libsyck source code; if your system has a site-wide shared libsyck, it will not be used." What's worse, currently dev-perl/YAML-Syck appears to depend on: - libsyck, which it won't use because it's supposed to use the bundled chunks - dev-lang/ruby with no version specified. This appears to pull in 1.9, which doesn't actually come with libsyck either (so I'm told). IMO, dependencies should be corrected (removed) and YAML::Syck should be allowed to use its internal libsyck.
(In reply to comment #1) > What's worse, currently dev-perl/YAML-Syck appears to depend on: > > - libsyck, which it won't use because it's supposed to use the bundled chunks > - dev-lang/ruby with no version specified. This appears to pull in 1.9, which > doesn't actually come with libsyck either (so I'm told). > > IMO, dependencies should be corrected (removed) Dependencies removed in 1.200.0. Thanks
As pointed out by Jon, this package bundles libsyck source coded against which it's linked at compile time. Excerpted from the man page: CAVEATS The current implementation bundles libsyck source code; if your system has a site-wide shared libsyck, it will not be used. The other issue (ruby dependency) has been fixed by Torsten a while ago.
It should be fixed or removed. The bug remains open for tracking.
Still the case in 1.310.0