Bug 253277 – dev-perl/YAML-Syck bundles a copy of syck

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Diego Elio Pettenò (RETIRED) 2008-12-31 17:59:40 UTC]

Should use the system copy.

[Comment 1 Jon Portnoy 2012-01-02 20:36:46 UTC]

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.

[Comment 2 Torsten Veller (RETIRED) 2012-02-18 08:05:15 UTC]

(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

[Comment 3 Patrice Clement 2014-11-29 21:06:32 UTC]

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.

[Comment 4 Andreas K. Hüttel 2014-11-29 21:15:24 UTC]

It should be fixed or removed. The bug remains open for tracking.

[Comment 5 Andreas K. Hüttel 2019-10-02 21:30:29 UTC]

Still the case in 1.310.0