I wrote a blog post thoroughly explaining Perl module versions and agree
with the assessment and suggested method presented (though I have no
comment on the remedy).
http://blogs.perl.org/users/grinnz/2018/04/a-guide-to-versions-in-perl.html
-Dan
On Thu, Aug 6, 2020, 1:09 PM Tina Müller
On Thu, Apr 25, 2019 at 3:36 PM Petr Pisar wrote:
>
> Any opinions? Should we go with this change? Wich format do you like most?
>
I think this is a great idea, and the first option is most similar to
normal Perl lib paths.
-Dan
___
perl-devel
On Thu, May 24, 2018 at 1:03 PM, Petr Šabata wrote:
>
>
> Do we know if files like /modules/02packages.details.txt are
> still going to be provided by cpan.org? If not, virtually all
> CPAN tools will have to be updated. cpanspec included.
>
Yes. That file is on all CPAN
On Thu, May 24, 2018 at 12:34 PM, Petr Pisar wrote:
> On Fri, May 18, 2018 at 10:55:02AM +0100, Dave Cross wrote:
> > See https://log.perl.org/2018/05/goodbye-search-dot-cpan-dot-org.html
> >
> > This means that the URLs included in RPMs of CPAN modules will need to
> > change
On Wed, Jun 14, 2017 at 7:52 AM, Petr Pisar wrote:
>
> Therefore I offered them that Fedora can make "dnf install perl" working as
> thay want and it will be implemented by renaming perl-core to perl and
> giving a new name to present perl package.
>
> Thus I created this
Sorry I don't have quotes but I was not subscribed to the list yet.
Looking at the dependency chain for perl-core, it brings in perl-devel
directly and as a prerequisite for modules such as perl-ExtUtils-MakeMaker
and perl-ExtUtils-Miniperl. Assuming perl-devel is what brings in the C
development