You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of my wishlist items for the Perl Toolchain Summit this year, is to explore using PURLs as a way to both communicate resolved dependencies, and for specifying requirements (which should be possible once @pombredanne's version-range-spec branch is merge into purl-spec).
One likely consequence can be that this package becomes a whole lot more critical within the CPAN ecosystem since it might be placed waay up the CPAN dependency tree, with all the risks and responsibilities this entails.
If such a thing happens, would you be comfortable with this?
The text was updated successfully, but these errors were encountered:
Hei!
One of my wishlist items for the Perl Toolchain Summit this year, is to explore using PURLs as a way to both communicate resolved dependencies, and for specifying requirements (which should be possible once @pombredanne's version-range-spec branch is merge into purl-spec).
One likely consequence can be that this package becomes a whole lot more critical within the CPAN ecosystem since it might be placed waay up the CPAN dependency tree, with all the risks and responsibilities this entails.
If such a thing happens, would you be comfortable with this?
The text was updated successfully, but these errors were encountered: