configure_requires (or the subsequent changes to allow repository-controlled critical minimum versions) might potentially let us fix this problem as well.
One big problem at the moment is that the process for passing dependency information from the configuration script to the parent CPAN client is quite simplistic, just a single list of PREREQ values I believe. One potential solution to this, once we have configure_requires out there and working properly, would be to change the way we communicate between the configure script and the CPAN client to generate a "localized META.yml" instead of a custom mechanism for each configure system. So when the configure script runs it either updates the META.yml or generates a new file, lets call it MYMETA.yml purely for example purposes, that represents the metadata on the CURRENT machine, where the existing META.yml represents the metadata on the author's machine. There's some complexities in that though... for example some values in META.yml might only be able to be generated with the full author-side toolchain, and not be recreatable at install-time... Personally, I see the path we need to take from configure_requires to the next step (server-driven critical upgrades) but I struggle to see clearly where exactly to go after that, because we haven't seen what the fallout from configure_requires is yet. Adam K On 8/18/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote: > > # from Ken Williams > # on Monday 13 August 2007 07:41 pm: > > >The problem is that we've always defined testing as part of > >building. If we now split someone's test prereqs into test_requires > >and stop listing them in build_requires, then any tool that doesn't > >know about test_requires will miss that prereq and tests will fail. > > > >So if we did make this split, people would have to keep listing such > >prereqs in build_requires too. I suspect that would become confusing. > > Can that be accurately qualified as "to be compatible with older M::B, > people would have to keep ..." ? Is that solvable by > configure_requires? > > I'm wondering if there's a way that the code can do this for them. > > Perhaps I need a better understanding of how CPAN and CPANPLUS are > getting their information (_build/prereqs ?) > > And back to the retest thing: would it be useful to install the > META.yml as something generated during the build? This would get the > platform-specific bits down to a per-machine basis, no? > > --Eric > -- > The opinions expressed in this e-mail were randomly generated by > the computer and do not necessarily reflect the views of its owner. > --Management > --------------------------------------------------- > http://scratchcomputing.com > --------------------------------------------------- >
