On 2/1/06, David Ayers <[EMAIL PROTECTED]> wrote: > Chris B. Vetter schrieb: > > Then we _might_ have problems in case of ported applications if they > > use hard-coded directory names. Well, not really problems, but we > > might get two directories with the same 'functionality.' > Indeed, but the counter argument is that using hard-coded directory > names is a bug, just like any other. This becomes particularly apparent > whenever such directory names get localized (as some wide spread > proprietary operating systems actually do). > IMO, I think the 'make' issue is probably a good reason to keep our > current scheme.
Absolutely true, but experience shows that this will happen again, and you cannot count on the 'porter' to remember each and every 'pitfall.' Even (somewhat) 'official' GNUstep applications and frameworks, e.g. Addresses, use hard-coded directories. That especially becomes obvious if you install GNUstep using a different directory layout. In case of Addresses (v.0.4.6), there's a hard-coded reference to ~/GNUstep/Library/Addresses/. Bummer. -- Chris _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
