[haiku-development] Re: usr/bin

On Tue, Apr 28, 2009 at 9:04 AM, Marcus Overhagen
<marcusoverhagen@xxxxxxxx> wrote:
>> I also am aware of the difference between merely compiling something and
>> porting it, D'oh! But when a test suite uses Python and calls hundreds
>> of scripts with #!/usr/bin/env python then the sensible thing to do is
>> NOT edit the whole mess, but to install a simple symlink. I don't care
>> what the _proper_ way to do that might be, the return isn't worth the
>> effort when tests are run once and then immediately deleted once their
>> results are known.
>
> Your test method is flawed. The users won't have a symlink, so their
> result when running those scripts will be different from your result.
>
> However, editing the test suite certainly isn't the sensible either.
>
> I'm not sure if it's worth the effort to explain this, but certainly
> a sensible way to provide compatibilty with those scripts would
> be to implement a mapping inside the runtimeloader of the
> standard unix #! directories to haiku directories.

I've seen a few packages that even build their test scripts during
configure (just like the Makefiles...) - which seems like the proper
way to do it. That is after-all pretty much why configure scripts
exist, is it not?

- Urias

Other related posts: