Hi, Le 27 avril 2012 09:48, Jérôme Maloberti <[email protected]> a écrit :
> Hi, > > 2012/4/27 Sébastien Fricker <[email protected]> > >> >> Am 26 avr. 2012 um 19:06 schrieb Jérôme Maloberti: >> >> Who will test them ? >> I am maintaining 22 godi packages on my free time, and I am not even >> notified when a new version has been released. >> Are you implying that I should test all these packages regularly to be >> sure that they're still valid ? >> You can't be serious >> >> We have some scripts in Debian (uscan) that scans regularly for upstream version and reports new upstream. See for example, the column "watch" at the right of this pages: http://qa.debian.org/[email protected] Version in pink are the one that differs from Debian version. > >> 2) Verify that every packages compiles >> > > You mean after building the dependency and mutual exclusion graph ? > We also have this in Debian. We run regularly a whole archive rebuild. See an example reports here: http://piuparts.debian.org/sid/ Now, for the "why GODI doesn't do it ?" part. Piupart is run on a cluster of 5000+ computer and it takes at least a day to compile. GODI is a lot smaller but will have less computer. And piupart is an already pretty big piece of code. In general, Debian has a 800+ people workforce, which is not the case of GODI. Setting watch file, running them and fixing bugs on its own is a full time job. So, solutions exist and can be applied, though I think that we need more workforce to apply all the suggestion of Sebastien. It is not as easy as it seems. (Though, OASIS-DB will provide some solution esp. regarding watch/uscan but it is not yet here and we should not rely on it for now). Cheers Sylvain
_______________________________________________ Godi-list mailing list [email protected] https://godirepo.camlcity.org/mailman/listinfo/godi-list
