Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: frozen-bubble - Frozen Bubble arcade gam
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202439
------- Additional Comments From wart(a)kobold.org 2006-08-20 15:46 EST -------
(In reply to comment #17)
I think moving the files but leaving the perl(...) Provides in is
worse than
leaving the files in the usual locations (and leaving the Provides intact).
Moving should be coupled with Provides (and probably Requires due to comment 8)
filtering but that's of questionable gain anyway, I'd revert moving the files
and doing things as usual.
My main concerns with leaving the files in %{perl_vendorarch} is that these are
application-specific perl modules. They have no use outside of this package. I
strongly prefer moving things like this into application specific directories
such as %{_libdir}/%{name} instead of polluting the language library tree.
I know languages like python and Tcl can handle this with no problem, which is
why I advocated doing it here as well. It seems to me that we have two choices
here:
1) Move the files to %{_libdir}/%{name} and turn off the
autoprovides/autorequires for the perl modules
2) Leave the files where they are and live with obscurities like perl(fbsyms)
and perl(fb_c_stuff) in the system-wide perl library tree.
If the current standard practice for app-specific perl modules is #2 then I
won't argue, even though I think it's a bad policy.
--
Configure bugmail:
https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.