#19 Sandbox

open
nobody
None
5
2001-10-01
2001-10-01
Anonymous
No

Make a sandbox version of XDarwin which doesn't
install or use anything in /usr/

The primary reason for doing this is convenience
for the user. Frameworks are easier to install and
can be localized. If I install X11.framework in ~/
Library I can copy my Library folder to another
volume and everything still works. Otherwise I have
to reinstall everything using XFree86's extra-
crummy installer.

(the XF4 installer is SO crummy it breaks if its pwd
has a space in it!)

Structure:

X11.framework/Versions/R6/X11 (libX11)
...other libs
X11.framework/Versions/R6/Headers/...
X11.framework/Versions/R6/Resources/
XDarwinStartup
X11.framework/Versions/R6/Resources/XDarwin
X11.framework/Versions/R6/Resources/etc/...

Some libs may be broken up like
ApplicationSupport.framework is:

X11.framework/Versions/R6/Frameworks/
Xm.framework/...

Discussion

  • Torrey T. Lyons

    Torrey T. Lyons - 2001-10-04

    Logged In: YES
    user_id=133579

    This is not hard to do, but would be of little use. All the X
    applications that have been ported for Darwin/Mac OS X would
    have to be ported again at significantly higher trouble,
    because they all expect to find their libraries and headers
    in standard places like /usr/X11R6. You would have a nice,
    easy to install version that nothing would work with.
    Unfortunately, on this one we follow Apple's lead and don't
    try to use frameworks for legacy code where there is already
    a well establish tradition for where everything should be
    placed.

    On the other hand, making a nicer GUI-based installer is a
    good thing to do that will definitely happen. I have heard
    there are various versions out there already floating around
    on the web.

     
  • Nobody/Anonymous

    Logged In: NO

    Considering how few X11 apps I have to use, I don't
    consider that an issue.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks