> On 7 Jan 2010 Peter Naulls wrote: > > alan buckley wrote: > >> The problem is the unixlib package and the !UnixLib it installs >> contains the SharedUnixLibrary module. If you conflict with the >> unixlib package then all packages that depend on it will be >> removed when you uninstall it to install the new >> sharedunixlibrary package. You could have a conflict between >> gcc4 and the development unixlib package (I'm not sure what >> its called at the moment UnixLib-Dev?), but not the unixlib >> package. > > No, not at all. You wouldn't get the uninstalls, since you'd > provide the dependency - either with a new package, or a > "Provides:" field. I don't know if you've used packaging > on Linux systems or not, but this is done a lot. But it > does have to be done carefully when there are complex > dependency setups. I think we are talking at cross-purposes a bit here. I'm just saying that with libpkg as it is at the moment, you can't put in the conflicts with the UnixLib package or you will have the consequences I outlined. You are telling me what a solution would be if we changed libpkg. So for the current GCC/SharedUnixLibrary packages we can't have the conflict, but we should change to your scheme when libpkg has been updated.
> >> I think it should be camelcase or lowercase, not upper case >> for all letters. > > Well, that really depends. e.g. "GCC", or other acronyms, > and it may come down to a matter of taste at the time. One > risk here is the issue we already ran into - inconsistent > caps are easy to make a mistake with - sometimes the > middle caps is a matter of author preference - e.g, "NetSurf". > In Debian, enforcing all lower case avoids this, but the > complicating factor in RISC OS is a case-insensitive filing > system. Perhaps making the package name matching case-insensitive > too would be a good move. > This just shows how complicated this is and down to personal taste. I would have said GCC was all capitalized as its an acronym even if the general principle was to use camelcase. Making the package name matching case insensitive would help, but it may cause problems for secondary task like generating web page links etc. Regards, Alan _________________________________________________________________ Tell us your greatest, weirdest and funniest Hotmail stories http://clk.atdmt.com/UKM/go/195013117/direct/01/ _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
