SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The FHS guys in their infinite wisdom decided that it's ok for applications to dump secondary executables and suchlike in /usr/lib/<appname> rather than /usr/libexec. Personally I'm with you and would much rather see a /usr/lib that only contains things ending in .so or .a but those days are gone.
My personal preference is for the debian way of doing multilib with a /lib and /lib32 on 64bit systems, which would have avoided the ugliness we see on Slackware with the artificial /lib /lib64 split.
It's not a big deal, just a matter of aesthetics (much like not having non-libraries in /usr/lib).
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Original Poster
Rep:
if I look in the glibc.SlackBuild (64bit even)
you find the following patch being used:
# Use old-style locale directories rather than a single (and strangely
# formatted) /usr/lib/locale/locale-archive file:
zcat $CWD/glibc.locale.no-archive.diff.gz | patch -p1 --verbose || exit 1
even the patch suggest that the locale directory would be in /usr/lib/locale
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Original Poster
Rep:
I just checked the whole glibc source.
in the ChangeLog.10 this is mentioned.
Code:
* sysdeps/unix/sysv/linux/configure.in: For sparc64, put locale
stuff into $exec_prefix/lib/locale because it can be shared between
32bit and 64bit libraries.
Well glibc is the provider, but main user is gettext.
gettext expects to find locale definitions in /usr/lib/locale or /usr/lib64/locale depending on the architecture and translation files in /usr/share/locale/<locale>/LC_MESSAGES, unless TEXTDOMAINDIR be set to another value than the default /usr/share/locale.
Because many different languages for many different packages have to be stored we need some way to add these information to file message catalog files. The way usually used in Unix environments is have this encoding in the file name. This is also done here. The directory name given in bindtextdomains second argument (or the default directory), followed by the name of the locale, the locale category, and the domain name are concatenated:
dir_name/locale/LC_category/domain_name.mo The default value for dir_name is system specific. For the GNU library, and for packages adhering to its conventions, it's:
/usr/local/share/locale locale is the name of the locale category which is designated by LC_category. For gettext and dgettext this LC_category is always LC_MESSAGES.3 The name of the locale category is determined through setlocale (LC_category, NULL). 4 When using the function dcgettext, you can specify the locale category through the third argument
My personal preference is for the debian way of doing multilib with a /lib and /lib32 on 64bit systems, which would have avoided the ugliness we see on Slackware with the artificial /lib /lib64 split.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.