Jon Wilson escribió: > > No, I agree that conservative is a good step (I'm not really a fan of the > > breaking away from the kernel development branch, for instance). As long > > as there are frequent updates to the released unattended versions (4.5 was > > around for a long long time) it shouldn't be a problem. In the past, I've > > had to compile it myself for newer kernel versions (network drivers, etc). > > If you feel that it is too too conservative, maybe it would be worth while > > to have a development branch (bleeding edge) that developers can test with > > and patch, and then the stable, slowly progressing branch as well (but > > thats more overhead as well).
Well, 4.7 release took a while, 4.8 release was quicker to setup. I also thought that maybe using something > > like buildroot, and compiling unattended in a sort of embedded system style > > might make it so we could compile older program versions (like 2.3.6) on > > the newest system versions. I like this idea, Have you got any examples where to start?. Some people on this list had problems because there were not using the same version as I do. So this is a good thing to have. :-) ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
