On Thu, 4 Mar 2004 04:57, Adam Fedor wrote: > On Wednesday, March 3, 2004, at 12:54 AM, Sheldon Gill wrote: > >> I'd like to keep support for the root .GNUsteprc file as well, at > >> least > >> until we decide to depreciate it. > > > > I thought that now was right time to do so. It does not add > > functionality, > > but the same level is provided by the new GNUstep.conf along with other > > benefits. One might consider the new configuration file a sort of > > upgrade of > > the old one, albeit one which requires changes and moving the file. > > > > I think having a root .GNUsteprc which can over-ride GNUstep.conf > > makes things > > more complex without giving us any benefits. > > Yes, that's true, but I'd like to keep one release cycle between > depreciating it and removing it. I bet no one is actually using it, > but now-days I'm often surprised by the number of situations GNUstep is > used in.
As a user, if you've got a GNUSTEP_SYSTEM_ROOT/.GNUsteprc file then you need to edit GNUstep.conf to match. That's the only imposition and it needs to be done when .GNUsteprc is dropped. That either happens in this cycle, or the next. I don't see any benefit in delaying the imposition. The effect for users will be the same. On the other hand, continued though deprecated support for the root .GNUsteprc will mean spending hours adding and debugging code to handle it properly. Those hours are, IMHO, better spent elsewhere. I agree that a release cycle between deprecating and removal is desirable in general but not in this specific case. Regards, Sheldon _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
