From: Erin S. <si...@ha...> - 2002-10-24 15:26:09
|
Marc Groot Koerkamp said: > > Yesterday I started my own branche and like you did with SM_PATH I > introduced > SM_LIB_PATH to achieve that at a later time parts of SM can be moved > out the > document root and can be placed in /usr/local/squirrelmail/lib or > something > like that. > > After some thinking I thought we have to remove all the relative > links and > define SM_PATH absolute. > > That way we can define SM_LIB_PATH, SM_SERVICES_PATH, > SM_TEMPLATES_PATH etc > etc. The plugins only have to include sm_init and all the paths are > automaticly defined absolute. I disagree strongly. I feel the links should remain relative. I saw what you did with the SM_LIB_PATH, and, frankly, didn't see much value in it (aside from programmatical clarity). But as you said, it was your branch.. ;) Yes, it would be nice to share templates, etc. between installations.. but a savvy admin can do this just as easily with a few well placed symbolic links. I think the SM install should remain a self-contained entity, and relative links are the only way to make sure that the SM entity will always work regardless of where the admin places it. I personally like I can move an SM install around at will without worrying about updating path values. It makes migration (or copying an install over multiple boxes) a lot easier as well.. Basically, I don't like the idea of going to absolute paths for all of the reasons that were outlined when we discussed paths, and came up with the SM_PATH variable in the first place. ;) My vote, for absolute paths, is NO. Erin (sizzle) -- 'Waste of a good apple.' ~Samwise Gamgee (ICQ: 36870353) |