[oi-dev] Any reason to keep Studio indent in /usr/bin

[Bruce Lilly]

I think (I'm away from my OI machines at the moment) it actually is in
/opt/ccs/bin.

I know it's broken; it changes valid code such as

unsigned int foo = 0U;

into broken gibberish (it breaks apart the 0U token.

My recommendation is to avoid symlinks; install each in an appropriate
place and allow users to decide order of preference via PATH.

On Thu, Feb 5, 2015 at 1:10 AM, Alexander Pyhalov <alp at rsu.ru> wrote:

> Hello.
> We currently ship symlinks to Studio indent in /usr/bin. I had to use GNU
> indent to build Mesa 9.0.3. I see that new Oracle Solaris versions ships
> GNU indent as /usr/bin/indent. Any reason for us to keep Studio indent
> there?
> As for reasons to avoid keeping it in /usr/bin - it's some closed source
> binary blob, and I can't use it to build Mesa.
> Another decision - ship GNU indent to /usr/gnu/bin and to create mediator
> on indent implementation. But do we really need one?
> (I suppose to ship old one in /opt/sunstudio12.1/prod/bin/indent (as it's
> shipped now) and keep /opt/sunstudio12.1/bin/indent symlink).
> --
> System Administrator of Southern Federal University Computer Center
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20150205/172e3329/attachment-0005.html>