[csw-maintainers] bad interactions with CSWcommon

[Ben Walton]

Excerpts from Philip Brown's message of Sun Jun 20 11:06:43 -0400 2010:
> it's interesting to note, that the example you give where coreutils
> does deliver two individual, separate files...(in locale/vi) does NOT
> have the common level symlink for that locale !

Huh?

# grep locale/vi /var/sadm/install/contents | grep coreutils
/opt/csw/share/locale/vi/LC_MESSAGES/coreutils.mo f none 0644 root bin 327678 49246 1274322262 CSWcoreutils
/opt/csw/share/locale/vi/LC_TIME d none 0755 root bin CSWcoreutils
/opt/csw/share/locale/vi/LC_TIME/coreutils.mo=../LC_MESSAGES/coreutils.mo s none CSWcoreutils

# find . -name coreutils.mo -ls
186123  328 -rw-r--r--   1 root     bin        327678 May 19 22:24 ./LC_MESSAGES/coreutils.mo
599924    0 lrwxrwxrwx   1 root     root           27 May 20 19:25 ./LC_TIME/coreutils.mo -> ../LC_MESSAGES/coreutils.mo

This one doesn't get broken as cswcommon doesn't provide any locale
files in vi.  However, the point remains that while symlinks will work
in this case as coreutils delivers all .mo data as a single file, it
is _valid_ for a package to provide separate files.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302