Codepage directory definition is a mess with Samba 3.3

[Herwig Bauernfeind]

In Samba 3.3 the location definition of the codepage files (upcase.dat, lowcase.dat and valid.dat) results in a mess:

We define the codepages directory to be a directory named "codepages" as a subdirectory of the executable directory.

The result is that depending upon which component is looking for the files they are searched in the following places:

ndpsmb.dll via EVFSCTL.EXE: x:\ecs\bin\codepages\*
ndpsmb.dll via NetDrive:    %NDFSDIR%\codepages\*
Any Samba executable:       exedir\codepages\*

Considering there are likely the commandline utilities installed another set is searched at x:\ecs\system\samba\codepages\*

Proposed solution: Let's move the codepages directory to %ETC%\samba\codepages similar to the way we have done it for other Samba data files.

[Herwig Bauernfeind]

GIven the fact that in Samba 3.0 these files were in exedir\lib the average Samba user might end up with half a dozen of sets of these files...

[Silvan Scherrer]

given the fact, that we never delivered those files with the client, i'm almost 100% sure they are not needed. the server always finds them. moving it to the 3.5 line of code, as we will fix it there.

[Herwig Bauernfeind]

Changeset #680 fixes this for Samba 3.3
Changeset #681 fixes this for Samba 3.5