On 4/11/07, James Carlson <[EMAIL PROTECTED]> wrote:
I. Szczesniak writes:
> On 4/11/07, James Carlson <[EMAIL PROTECTED]> wrote:
> > I. Szczesniak writes:
> > > I explained this in another mail. Our statistics show that lots of
> > > customers do not have SUNWxcu4 installed. The system scripts do not
> > > require this package and customers tend to remove unused packages from
> > > their systems.
> >
> > What would satisfy your complaint?
>
> Make sure that the tools in /usr/xpg4/bin are treated with the same
> level of support as the tools in /usr/bin and merge the SUNWxcu4
> package into SUNWcsu.

I'm confused.  They *do* have the same level of support.  Can you
explain why you think they're supported differently?

SUNWxcu4 is a separate package which is IMO wrong. The package should
be merged into SUNWcsu and system scripts should use
/usr/xpg4/bin:/usr/bin as PATH, not /usr/bin.

> > We could make the system less configurable by forcing SUNWxcu4 into
> > SUNWCmreq or by just removing SUNWxcu4 and putting the binaries into
> > SUNWcsu.  Would that help?
>
> It would help if system scripts use /usr/xpg4/bin:/usr/bin as their
> default path. This would at least ensure that such scripts will work
> with multibyte locales.

You can do that today.

No, I cannot do that without modifying all script myself.

Now, what those scripts are doing with multibyte locales is a bit of a
mystery to me.  I had thought that was an issue for user processes,
not system scripts.

Ask yourself: What will happen if a system script encounters a file
name with multibyte characters.

> > If not, then just what are you asking for?  To have /usr/bin change
> > incompatibly?
>
> I don't think this will happen without a major shift to a more
> customer-friendly policy at Sun.

We obviously have different notions of what "friendliness" entails.

The inability to handle multibyte characters is very
customer-unfriendly. In some countries like Taiwan it is considered a
serious offense.

Irek
_______________________________________________
opensolaris-discuss mailing list
[EMAIL PROTECTED]

Reply via email to