Am 17.02.2013 15:04, schrieb Jacob Carlborg: > On 2013-02-17 13:58, Sönke Ludwig wrote: > >> But that would need to happen as a separate step and then there would be >> two redundant files in the repository, with the usual danger of >> inconsistencies between the two. > > The tool generates the JSON/Yaml/XML from the D script. The user never > have to see the Json file. >
But the registry gets its information about a package directly from the github repository (this is quite a central idea), so it must also be committed there. >> Since a build script may behave differently on different systems, it >> could also happen that the contents cannot really be described as >> JSON/XML. For example someone might get the idea to search the system >> for some library and only add a corresponding dependency if it is found. >> There would be no way for the registry to represent that. > > Sure, it's always possible to do stupid things. > But at least not this particular this with the data driven approach ;)
