> If you want to keep a "pure" Unix system hierarchy (which is my intention)
> you should try to keep all elements on the place
> where they are expected. This means no additional appendizes just because
it
> is technically opportune.
> If I wanted a unclean file system, I could change to DarwinPorts or Fink
;)
Just to show what I mean:
My idea is to implement a better MacOS GUI integration of Gentoo installed
tools.
This means real app folders which contain the actual GUI and which call the
correct Unix executables.
These packages could either directly packages in ebuilds, or they could be
external packages which are dependent on the actuall application.
I.e. something like
depends on
ghostscript-gui <----- ghostscript
In a non-prefixed approach, I can be sure that there will exist an
executable /usr/bin/gs, which I can call.
What I am to do in a prefixed system? Hope that the users did not forget to
call setenv-gentoo on bootup?
Start a local shell which calls setenv-gentoo, which maybe itself be
somewhere on
/Volumes/usbdrive/.hidden/far_away/big/long/path/to/gentoo/bin/setenv-gentoo
And do a exec "/bin/sh gs"? This sounds like a rather big security problem
to me, because nothing stops any malware to change things like
the path variable.
Regards
Dirk
--
[email protected] mailing list
