?b 日, 2003-10-26 15:32, Stas Bekman ?g?D?G > I think there is a different reason for not providing all the version numbers. > I've explained my proposal in the last reply. We shouldn't delegate the > selection of the right generation to the client, because it doesn't have that > information.
I beg to differ. For example, suppose my Encode::HanConvert module works with Encode 1.70 and later, but does _not_ work with 1.97 and 1.98 due to their bugs. I'm also confident that 1.99 will fix it, but 1.99 is not released yet. So, I'd like to say: requires: '>= 1.70, != 1.97, != 1.98' in my META.yml and PREREQ_PM, regardless of their generations. In fact, I think CPANPLUS cannot reasonably deal with such a requirement, without a full list of version numbers and corresponding distinfo. > > Maybe some sort of concrete numbers will be better. I'll see what I can > > do. > Autrijus, if you don't mind I'd like to spec out those things first and only > then implement them. So we know for sure that we talk about the same thing. > Thank you. Oh. Okay, then. I was not talking about modifying PAUSE, but trying to measure how much will 02packages.txt.gz really "bloat up" by my proposal. But okay, we should talk first. Thanks, /Autrijus/
signature.asc
Description: =?UTF-8?Q?=E9=80=99=E6=98=AF=E6=95=B8=E4=BD=8D=E5=8A=A0=E7=B0=BD?= =?UTF-8?Q?=E7=9A=84=E9=83=B5?= =?UTF-8?Q?=E4=BB=B6?=