From: "Dirk Schönberger" <dirk.schoenberger@sz-online.de>
To: <gentoo-osx@lists.gentoo.org>
Subject: Re: [gentoo-osx] New document: Project targets
Date: Wed, 14 Dec 2005 23:56:20 +0100 [thread overview]
Message-ID: <013401c60101$9e907460$14b2a8c0@rincewind> (raw)
In-Reply-To: 010e01c600fe$7725d8a0$14b2a8c0@rincewind
> 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
--
gentoo-osx@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-14 22:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 9:01 [gentoo-osx] New document: Project targets Grobian
2005-12-12 16:36 ` Nathan
2005-12-12 18:00 ` Grobian
2005-12-12 18:21 ` Nathan
2005-12-12 19:29 ` Grobian
2005-12-14 19:11 ` Marcin Gabrowski
2005-12-14 19:22 ` Grobian
2005-12-14 20:18 ` Marcin Gabrowski
2005-12-14 20:26 ` Grobian
2005-12-14 21:22 ` Dirk Schönberger
2005-12-14 21:27 ` Nathan
2005-12-14 21:29 ` Dirk Schönberger
2005-12-14 21:39 ` Grobian
2005-12-14 21:43 ` Nathan
2005-12-14 22:01 ` Dirk Schönberger
2005-12-14 22:12 ` Nathan
2005-12-14 22:33 ` Dirk Schönberger
2005-12-14 22:56 ` Dirk Schönberger [this message]
2005-12-14 23:06 ` Nathan
2005-12-14 23:36 ` Dirk Schönberger
2005-12-15 7:22 ` Grobian
2005-12-15 8:33 ` Dirk Schönberger
2005-12-15 15:02 ` Dirk Schönberger
2005-12-15 15:10 ` Grobian
2005-12-15 7:12 ` Grobian
2005-12-14 23:02 ` Marcin Gabrowski
2005-12-14 23:42 ` Dirk Schönberger
2005-12-15 0:35 ` Marcin Gabrowski
2005-12-15 7:27 ` Grobian
2005-12-15 8:27 ` Dirk Schönberger
2005-12-15 9:36 ` Marcin Gabrowski
2005-12-15 9:47 ` Dirk Schönberger
2005-12-15 11:17 ` Marcin Gabrowski
2005-12-15 14:29 ` Grobian
2005-12-14 21:31 ` Grobian
2005-12-12 19:46 ` Grobian
2005-12-13 9:03 ` Grobian
2005-12-15 20:28 ` Grobian
-- strict thread matches above, loose matches on Subject: below --
2005-12-13 13:37 Dirk Schönberger
2005-12-14 5:41 ` Finn Thain
2005-12-14 9:10 ` Dirk Schönberger
2005-12-14 19:12 ` Marcin Gabrowski
2005-12-14 19:25 ` Grobian
2005-12-14 19:58 ` Marcin Gabrowski
2005-12-14 19:15 ` Marcin Gabrowski
2005-12-16 15:09 Dirk Schönberger
2005-12-16 15:17 Dirk Schönberger
2005-12-16 15:24 ` Grobian
2005-12-16 15:30 ` Dirk Schönberger
2005-12-16 17:40 ` Grobian
2005-12-16 21:02 ` Dirk Schönberger
2005-12-16 22:16 ` Grobian
2005-12-16 22:36 ` Dirk Schönberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='013401c60101$9e907460$14b2a8c0@rincewind' \
--to=dirk.schoenberger@sz-online.de \
--cc=gentoo-osx@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox