On 03/10/2011 06:07 PM, Johnny Hughes wrote: > An example is the issue we were having today with util-linux on the 5.6 > build. That's *precisely* the kind of thing that I'm talking about. Narrow stuff which, exactly as you point out, will probably never be relevant again in the future, but would still be very useful to anyone working on the current release. I'll give you one back: https://bugzilla.redhat.com/show_bug.cgi?id=683102 Too impatient to wait for CentOS 6, I installed a trial version of RHEL 6 on my workstation thinking that CentOS would be out anyway by the time I need updates. But it wasn't. And there are some critical ones out. And my trial subscription has long expired. So there's only one way to deal with this: respinning from source. I've been doing that in the past couple of days, either repeating work that you have already done or preceding it without any benefit to you. That's where this discussion comes from. > If I listed this on the wiki, I would also have to remember to change it > when it is no longer applicable. It is already listed on the RHEL > bugzilla site, so if I search for it there the next time I have the > problem (if there ever is a next time) it will still be there. Having it all in one place makes collaboration much easier. It allows me to profit from your work and you to profit from mine and that of others. For example, the bug above is totally trivial, but in my build it was triggered just after I went to bed, wasting a night and a day of the machine idling instead of compiling. If you know about it, it might save you and everybody else an extra day of waiting. That's what the benefit of an open build process would be. Z