On Tue, Sep 27, 2005 at 10:20:15AM -0500, Chris Dolan wrote: > A Perl module I'm trying to package depends on Pod::Perldoc v3.14. > Earlier versions of that module are provided by the core Perl (e.g. > v3.13 is in Perl 5.8.6 and v3.10 is in Perl 5.8.1), however our Perl > packages (e.g. perl581.info) do not list pod-perldoc-pm in the > Provides area. > > If I do package pod-perldoc-pm v3.14: > * Do we need to update perl58x.info to add Provides/Conflicts for > pod-perldoc-pm? > * Does my package need to Conflict with perl581-core? > * Does my package need to be Perl-versioned?
Since there's no existing pkg for this namespace, you get to set it. Your pkg only needs to be perl-versioned as per the usual rules (it contains compiled C or it Depends on a perl-versioned pkg). perlXXX-core is installed in a separate location from where packaged perl modules go (%p/lib/perl5-core instead of %p/lib/perl5), so no Conflicts or Replaces is necessary here. If you think it would be useful to have the various perlXXX-core Provides:perl-poddoc-pm (or -pmXXX) we can certainly do so. OTOH, assuming your actual perl-poddoc-pm is simple and has few Depends, I'm not sure it's worth forcing users to recompile their perl core pkg just to prevent their having to install a small module to satisfy "Depends:perl-poddoc-pm". dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
