Re: CMSP 14. Prerequisites should be mutually exclusive
David Golden wrote: Modules should only be listed once across all prerequisite categories. Strongly opposed. It's possible for a single module to be required in more than one phase, possibly for independent reasons and possibly with different minimum versions. If the module must be listed only once then the dependencies that an install tool must gather for one of the phases would have to implicitly include all the dependencies listed for the other phase. It would grossly compromise the separation of phases. -zefram
Re: CMSP 14. Prerequisites should be mutually exclusive
* David Golden xda...@gmail.com [2009-10-09T07:48:50] 14. Prerequisites should be mutually exclusive No vote, no strong opinion. -- rjbs
Re: CMSP 14. Prerequisites should be mutually exclusive
David Golden wrote: 14. Prerequisites should be mutually exclusive * I think this would remove a certain amount of useful flexibility, standard light weight META Object modules could easily automate the production of the merged list. This feels like sacrificing on a fundamental point to make life easier when you don't have tools that haven't been written yet --Adam K -1 What Adam said. Steffen
Re: CMSP 14. Prerequisites should be mutually exclusive
On Oct 9, 2009, at 6:55 AM, Graham Barr wrote: Modules should only be listed once across all prerequisite categories. E.g. a 'requires' module shouldn't be listed in 'test_requires'; a 'configure_requires' module shouldn't be listed in 'build_requires'. Instead, the spec should define which combinations of categories should be available at which stages of the install process. (Dagolden) I do not see the benefit of forcing such a requirement. -1 -1 David
