On Thu, 25 Apr 2002, Ben Reser wrote: > Yes and they normally are. But if Stew is say a month behind you and he > makes a patch and releases a 2.4.18-6.2mdk kernel and you're already on > 12mdk there can be one heck of a lot of difference between the two.
Yes, kernel is another problem. AFAIK, Stew usually send patches for kernel release N, but Juan includes them for N+2 since N+1 is usally already on the way at this time. Yes, things that worked at release N could break at release N+2. I believe kernel changes should be notified and while kernel N+2 is building on x86, SRPMs should be generated and propagated to other arches, for build checking. > Uhh PPC != ia64. Yes, but the process is likewise. > And what's on your private machines is not neccessarily available to the > rest of the world. > > [breser@stream SRPMS]$ pwd > /mirror/linux/mandrake/Mandrake/8.1/SRPMS > [breser@stream SRPMS]$ ls -l ia64 > > [breser@stream ia64]$ pwd > /mirror/linux/mandrake/Mandrake/8.1/ia64 > [breser@stream ia64]$ ls -l SRPMS > ls: SRPMS: No such file or directory Hmmm, probably that directory didn't get propagated to the primary mirror. Warly? That should be Mandrake/8.1/ia64/Mandrake/SRPMS though I'd prefer Mandrake/8.1/SRPMS/ia64/ too, on mirrors. > You totally ignored my GPL point. I haven't. > It's pretty silly that I've tried to come up with a solution for > everyone's desire to have PPC SRPMS but at the same time tried to be > reasonable about not wasting gobs of space on the mirrors That's the actual solution I explained to you.
