Andreas Vox <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
>>
>> Andreas Vox <[EMAIL PROTECTED]> writes:
>
| ...
>> | The idea is to try a hardcoded list of additional directories
>> | (currently /usr/local/bin, /opt/local/bin, /sw/bin
>> | and /usr/local/teTeX/bin/powerpc-darwin-current)
>> | if some executable is not found in the normal path.
>> | If this succeeds, the corrseponding directory is included in the
>> | path_prefix and later written to lyxrc.default.
>>
>> I am not really sure that I like this.
>
| The hardcoded-bit or the fact that a default for path_prefix
| is provided?
The hardcoded bit.
>> What I am uncomfortable with is what dirs to add... IMHO it would be
>> better to just have a configure options where you can add your own.
>> And really... this is the packagers task. Not ours. F.x. for linux/rpm
>> this should be done in the rpm spec.
>
| Packaging works differently in the Mac and Windows world. Especially
| with Mac there are 3-4 possible location where TeX could have been
| installed. Do you expect to have 3 different LyX packages for Mac?
| Also on Mac the installation is usually just a drag-and-drop action,
| there's no configure && make && make install (at least not for normal
| users :-) )
I expect it to be a similar system to rpm. A package system/installer.
IMHO it is the task for this packager to setup the proper defaults.
Sure we can have it in LyX: 3 paths for macos... X for win, X for
cygwin, X for unix.
Btw. Why only 3?
| Rationale:
| The lib/configure script searches for installed binaries on the given
| system. On Mac and Windows it can not rely on the environment path
| to be complete (not even remotely!). So lib/configure has to include
| additional directories for its search. Maybe this list could be configured
| before compilattion with a "--with-runtime-path-prefix=..." option.
| Once lib/configure finds a binary in one of these additional directories
| it is natural to include this into the default path_prefix.
| Mac and Windows users usually don't adjust the environment path on
| their own. On Mac it is near impossible anyway. That was the reason
| to implement the path_prefix in the first place. The current way --
| start LyX in non-functional mode, set the path_prefix in preferences,
| save preferences and restart LyX -- will not be acceptable to end users.
>
| Could I convince you?
I am not convinced.
The "--with-runtime-path-prefix" is more what I am looking for.
(or a --with-additional-runtime-path)
--
Lgb
