Re: podlators 5.00 released
On Mon, Dec 26, 2022 at 5:38 PM Russ Allbery wrote:
> Leon Timmermans writes:
> > That said, I would really appreciate it if in the future people would
> > talk a bit more with their upstreams when incrementing their perl
> > dependency; this could easily have been not so easy to work around.
>
> Is there a forum in which this sort of conversation takes place? I would
> be happy to have this discussion; I just don't know where to do it. Maybe
> perl5-porters, which I haven't been subscribed to for some years (although
> I send release notifications here) because it used to be super-high
> volume, but maybe it's not any more?
>
I guess p5p would have been the most obvious place to have this discussion
in this particular case. Toolchain doesn't really do email for some reason.
> Anyway, the reason why I thought this was safe is because Pod::Man is part
> of Perl core, so it's always available. I assume the problem is that
> Module::Build is requesting a later version than what comes with Perl in
> 5.8 (for Unicode support), and CPAN doesn't have the same support that
> PyPI has for providing multiple versions and being able to fall back on an
> older version if the newer version doesn't meet available constraints
> (such as not supporting the current version of Perl)?
>
Yeah, I can see where that assumption comes from.
> In the future, I would like to be able to use the package NAMESPACE VERSION
> syntax instead of $VERSION and the $foo->@* syntax instead of @{ $foo },
> so eventually it would be nice to require Perl 5.024 or later, although I
> know that's much too aggressive at the moment.
>
There's an interesting conundrum there. If the toolchain doesn't depend on
any new functionality you're not constrained there, but that also means
that any such new functionality goes largely unused.
Leon
Re: podlators 5.00 released
On Fri, Nov 25, 2022 at 11:53 PM Russ Allbery wrote: > - Drop support for Perl 5.8. The minimum required version is Perl 5.10. > It turns out that that part of the change made Module::Build uninstallable on 5.8, which makes half of CPAN uninstallable on 5.8. I resolved this by dropping the Pod::Man dependency (it was only needed for utf8-support on 5.8). That said, I would really appreciate it if in the future people would talk a bit more with their upstreams when incrementing their perl dependency; this could easily have been not so easy to work around. Leon
Re: Deprecation of alternate text in hyperlinks
On Mon, Jan 23, 2012 at 5:06 PM, Karl Williamson pub...@khwilliamson.com wrote: Version 1.50 of Pod::Parser adds a check and message indicating that Ltext|hyperlink is deprecated. This is based on the following sentences in perlpodspec, which has been there since its inception in 2001: Authors wanting to link to a particular (absolute) URL, must do so only with LEltscheme:... codes (like LElthttp://www.perl.org), and must not attempt LEltSome Site Name|scheme:... codes. This restriction avoids many problems in parsing and rendering LElt... codes. Elsewhere in the document, it says that the handler should handle these, as in the example LPerl.org|http://www.perl.org/ The new Pod:Parser has just been installed in blead, and about 10 pods run afoul of this new check, including things like Lperl...@perl.org|mailto:perl...@perl.org My question is should there really be a message for this kind of use, and if so, should it extend to mailto: links? The problem of us treating manpages as our designated documentation medium strikes us once again. IMO, it's time for perl's documentation to enter the 21st century and accept that hypertext has taken over. This kind of trouble keeps popping up (think of the lack of tables or proper support for images). I'm fine with reading my documentation on the console (I do it regularly), but by targeting the lowest common denominator we're cutting ourselves short. Leon
Re: Deprecation of alternate text in hyperlinks
On Tue, Jan 24, 2012 at 7:14 PM, Russ Allbery r...@stanford.edu wrote: Your rant against man pages is somewhat undermined by the fact that I, as maintainer of Pod::Man, have supported anchor text for URL L links from the beginning and opposed this restriction from the start. The restriction has nothing to do with targetting man pages. Then I was mistakenly assuming it was because of the manpages, my apologies. Leon
