Until this moment, we were considering two main possibilities when interpreting dependencies like Pango 1.8.0
One was to interpret it as Pango [1.8.0,1.8.0] Other possibility, currently (being used right now at CheckDependencies) is Pango [1.8.0,) Maybe we should (at least in the case of Recipes) interpret this line as Pango [,) I.e., drop the version number, and accept, by default, any version of that given program. If/when someone notices there is a lower/higher limit on version number, an updated recipe (containing, say, Pango [1.7,) at the Pango dependency line inside Resources/Dependencies) should be posted to gobolinux-recipes. _Maybe_ we could even start to drop the version numbers from the recipes being prepared (when there is not a known range). The idea would be: by default, we don't know the valid range of versions for a dependency program for a given program, and it is better to state is explicitly (i.e.: putting only the program name at the dependencies file) than putting also a version number that means almost nothing (just that this very version is known to be ok - BuildInformation file should be used for that*). * BuildInformation will only be placed inside binary packages? Or inside Recipes too? -- Andre Detsch _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
