On 5/27/07, Isaac Dupree <[EMAIL PROTECTED]> wrote: > Carlo Calica wrote: > > Testing the _version_ requirements is probably more difficult since > things can break in subtle ways with the wrong version, but at least it > could complain if the _build process_ ends in an error, with any > combination of versions allowed by stated dependencies (not just oldest > of everything, it might be nice to test randomized combinations of > possibilities perhaps). >
That's the most you can do automated. If there are unit tests you could run those. > > > > It sounds like you're talking about a build farm. Such a thing would > > be great. Iplementers talk to me. I'd really like to help with the > > efforts. > > I may look into this sometime. > > Unfortunately multiple architectures (even x86 vs x86-64) tend to > multiply the amount of work excessively. Hmm... since most things work > the same on all architectures, possibly some combination of > randomization, marking known-troublesome packages, spreading out the > workload over different-architecture systems (if there's an error then > go test everywhere)... could help. New package versions come out often > enough compared to how often something changes w.r.t > architecture-specificness or dependencies (I think), that it should be > okay for > Could be distributed. Since its only testing for failures (as opposed to building packages for general use) we can accept help easier. > > Would be great to get a SoC. > > We'll see what I'm feeling like then (and what Google thinks). Usually > in summers I rest and recover from the school year (but then, that > "resting" tends to involve feverishly programming / using my computer in > any case :-) > keep it in mind. Same thing for anyone else that qualifies. -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
