Hi Bernard, On Thursday 16 February 2006 18:35, Bernard Li wrote: > I was merely using it as an example. While I haven't tested RHEL3u6 > yet, I have tested the beta of RHEL4u3 and it is working fine.
Ah, then I misunderstood you. > However, I remember previously that we do not support a particular > update version of RHEL3, so I just want to make sure that we have > something in place to take care of this. > > But if you think this won't really happen, then that's fine too. Well... I think this would be really an exception case. We have no per-release package rpm subdirectories, and that would be overkill anyway. What I'm thinking of are simple tables: # if these compat_distro strings appear, the distro should work @compat_supported = qw( fc-4-i386 rhel-4-x86_64 ...); # # print warning message on these (real distro name used, including release!) @real_warning = qw( redhat-el-ws-3-4-x86_64 ...); So if fc-4-x86_64 is not in the @compat_supported table, die. But for the real distro-name redhat-el-ws-3-4-x86_64 print a warning message stating that there are known issues with it. RTFM or so. Would that match your requirements? Regards, Erich ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
