Hi Erich: On 2/2/07, Erich Focht <[EMAIL PROTECTED]> wrote:
> the check in the %pre script is a pretty bad idea, isn't it? It prevents us > from fixing this cleanly inside config.xml :-( Two ways seem clean to me: > Either take out the dependency entirely (also from the %pre) or take it in Andrea suggests changing the message from "error" to "warning" and also to take out the exit statement. This case, installation of systemimager-bittorrent will not fail and the bittorrent package will be installed after (since it is in config.xml) and everything is A-OK. Though if the user sets OSCAR_VERBOSE=3 or higher he will see the "warning" message and wonder what is going on... > cleanly, as dependency, and make the package distro dependent (but > noarch). The distro-dependency is not a big deal, actually the package should > be small. A pity that requires don't allow an || Actually, this could be solved if both bittorrent and BitTorrent packages provide a common package name, but I doubt this is the case... IMHO having the package distro dependent is the correct way to go since this will allow correct dependency resolution. It is a pity that RPMs generated in that case cannot be used cross-distro. Anyways, another solution as I have outlined is simply put bittorrent in prereqs. I have no particular feelings either way, but probably suggest the route with the least friction (i.e. changes :-) ) Cheers, Bernard ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
