On Sun, 30 Mar 2003, Rick Emery wrote: >> Facile answers like 'just build your own patch' aren't going to cut it >> in some corners of this school. This answer seems okay to experts on this >> mailing list. But in my experience this level of expertise is sadly lacking >> in the trenches, and I mean LACKING. > >Most people may not be able to build their own patches, but some will. And some >might make those patched rpms available to the rest of the community. > >I'm confident that someone will fill this void, much like freshrpms.net provides >packages that Red Hat doesn't. There might even be a business model in it; would >people be willing to pay to get upgrades for versions not supported by Red Hat >anymore? I'll bet somebody's already looked into it.
If people were willing to pay a reasonable price for such updates, they would be signing up for RHN IMHO. While someone could certainly try to follow the security scene, it would be a lot of effort to do so. Also, in order for it to be profitable for them, they would have to have credibility in the community, or they'd have to gain it. It's a lot more involved than just dropping a premade patch from the net into a src.rpm, bumping the version and building it. In order for any large body of people to be willing to pay for that kind of service, it will have to be reliable and of high quality. The price of that service will have to be high enough that anyone thinking of providing such a service finds it profitable enough that they are doing their job seriously, and are staying on top of things. You get what you pay for in this world. -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat -- Phoebe-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/phoebe-list
