Frederic Demians <frede...@tamil.fr> > Those kind of things can be tricky and messy. Something like a > dependency graph would be required, which is all but easy to implement. > It has something to do with how patches are applied with git: [...]
I think a different way of handling database updates is a good idea because it would remove the current serious chilling effect of claiming a dbrev when we're not sure if we have booked enough time to finish tidying, testing and sending (there's often some subtle bug shows up on the final peer review, isn't there?). Most systems running koha will have at least two depedency graph solvers installed: make and git. If we could harness one of those, that would be brilliant. Hope that helps, -- MJ Ray (slef) Webmaster and LMS developer at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
