Excerpts from Maciej Bliziński's message of Wed Aug 03 04:36:31 -0400 2011:
> I like the early detection of the issue. You could consider it a > build recipe check, as opposed to a binary package check. Fail fast is good, but doing the check in GAR removes the opportunity to intentionally have two the same. This isn't a likely scenario though. > Nevertheless, checking the resulting binary package set could be a > good idea. Something like "no two packages from the set under test > should have the same description field". As an extended check, > descriptions could be matched against all descriptions in the > catalog, but the database doesn't have the metadata yet. I would only look at the current set for a check like this. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ devel mailing list devel@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/devel
