OSX progress [potential BUG in SDL-devel package for OS X]

Why does the SDL-devel package for OS X install to my home directory as
root? This means I have to manually go back and change the ownership of
the directory to me.

Also does it need to run as root at all since it doesn’t install to the
/Library/Frameworks directory?

The Frameworks directory in ~/Library is owned by root because the SDL
Developer package installs as root. This is probably incorrect and is
preventing the SDL_image.framework from getting created in that
directory.

I think this will fix my problem if I change the ownership to my user
who owns ~ instead of the root user…

DaveOn Sunday, February 24, 2002, at 07:01 PM, Darrell Walisser wrote:

I can’t tell much from what the output. Is the file
"SDL_image.framework" under the build/ directory? The framework should
be copied to ~/Library/Frameworks/ in the build script.

-D

Why does the SDL-devel package for OS X install to my home directory as
root? This means I have to manually go back and change the ownership
of the directory to me.

Also does it need to run as root at all since it doesn’t install to the
/Library/Frameworks directory?

It has to run as root, at least I haven’t found a way to avoid this
yet). Remember that additional files are also installed (man pages and
html docs) which is why we have this requirement.

The Frameworks directory in ~/Library is owned by root because the SDL
Developer package installs as root. This is probably incorrect and is
preventing the SDL_image.framework from getting created in that
directory.

Not good. You have convinced me that I should investigate getting a
non-root installer or find a workaround. Anyone have any ideas? To
summarize, the issue here is that the installer runs as root (via sudo)
so some of the files are installed with sub-optimal permissions. A
workaround would involve either not installing as root (and giving up on
installing some files like man pages) or some UNIX trickery I haven’t
learned yet.

In theory we might install to /tmp (doesn’t require root) and move the
files around from there. But then we won’t be able to install the man
pages. Or we could figure out how to change the permissions of files
after the install (I’m not much of a UNIX guru so I don’t know the
answer to this). Essentially the install scripts are run with sudo, if
that helps any.

-DOn Sunday, February 24, 2002, at 09:38 PM, David Leimbach wrote:

Why does the SDL-devel package for OS X install to my home directory
as root? This means I have to manually go back and change the
ownership of the directory to me.

Also does it need to run as root at all since it doesn’t install to
the /Library/Frameworks directory?

It has to run as root, at least I haven’t found a way to avoid this
yet). Remember that additional files are also installed (man pages and
html docs) which is why we have this requirement.

The Frameworks directory in ~/Library is owned by root because the SDL
Developer package installs as root. This is probably incorrect and is
preventing the SDL_image.framework from getting created in that
directory.

Not good. You have convinced me that I should investigate getting a
non-root installer or find a workaround. Anyone have any ideas? To
summarize, the issue here is that the installer runs as root (via sudo)
so some of the files are installed with sub-optimal permissions. A
workaround would involve either not installing as root (and giving up
on installing some files like man pages) or some UNIX trickery I
haven’t learned yet.

Well the man pages are installed not in my home directory so why not
install the SDL library in the global directory as well? If anyone can
view the man pages shouldn’t they have access to the libs? What happens
if my system has 5 users with SDL-devel installed? One set of manpages
and 5 copies of the Framework doesn’t sit well with me either.

I would put the Framework in /Library instead of ~/Library. Same with
all other SDL related libs. That way everyone can benefit from it.

I don’t know maybe you would want to make that some kind of option.

In theory we might install to /tmp (doesn’t require root) and move the
files around from there. But then we won’t be able to install the man
pages. Or we could figure out how to change the permissions of files
after the install (I’m not much of a UNIX guru so I don’t know the
answer to this). Essentially the install scripts are run with sudo, if
that helps any.

If there is a way to get the userid of the person who originally
launched the installer before they keyed in the admin password then you
could “chown” the ~/Library/Frameworks directory to that UID in a post
install script.

That’s the best I can come up with on short notice.On Sunday, February 24, 2002, at 09:02 PM, Darrell Walisser wrote:

On Sunday, February 24, 2002, at 09:38 PM, David Leimbach wrote:

-D


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

My SDL_image install ended up in /Developer/Documentation/SDL,
try looking there. Is there a reason it ended up there?

-Randall LeedsOn Sunday, February 24, 2002, at 09:38 PM, David Leimbach wrote:

Why does the SDL-devel package for OS X install to my home directory as
root? This means I have to manually go back and change the ownership
of the directory to me.

Also does it need to run as root at all since it doesn’t install to the
/Library/Frameworks directory?

The Frameworks directory in ~/Library is owned by root because the SDL
Developer package installs as root. This is probably incorrect and is
preventing the SDL_image.framework from getting created in that
directory.

I think this will fix my problem if I change the ownership to my user
who owns ~ instead of the root user…

Dave

On Sunday, February 24, 2002, at 07:01 PM, Darrell Walisser wrote:

I can’t tell much from what the output. Is the file
"SDL_image.framework" under the build/ directory? The framework should
be copied to ~/Library/Frameworks/ in the build script.

-D


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

My SDL_image install ended up in /Developer/Documentation/SDL,
try looking there. Is there a reason it ended up there?

The old installers are broken. The new ones (not yet in CVS) fix this.

-DOn Sunday, February 24, 2002, at 11:24 PM, Randall Leeds wrote:

Holy cow! I have one there too.

This isn’t good. :POn Sunday, February 24, 2002, at 10:24 PM, Randall Leeds wrote:

My SDL_image install ended up in /Developer/Documentation/SDL,
try looking there. Is there a reason it ended up there?

-Randall Leeds

On Sunday, February 24, 2002, at 09:38 PM, David Leimbach wrote:

Why does the SDL-devel package for OS X install to my home directory
as root? This means I have to manually go back and change the
ownership of the directory to me.

Also does it need to run as root at all since it doesn’t install to
the /Library/Frameworks directory?

The Frameworks directory in ~/Library is owned by root because the SDL
Developer package installs as root. This is probably incorrect and is
preventing the SDL_image.framework from getting created in that
directory.

I think this will fix my problem if I change the ownership to my user
who owns ~ instead of the root user…

Dave

On Sunday, February 24, 2002, at 07:01 PM, Darrell Walisser wrote:

I can’t tell much from what the output. Is the file
"SDL_image.framework" under the build/ directory? The framework
should be copied to ~/Library/Frameworks/ in the build script.

-D


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

My SDL_image install ended up in /Developer/Documentation/SDL,
try looking there. Is there a reason it ended up there?

The old installers are broken. The new ones (not yet in CVS) fix this.

I’ve updated the PBProjects in CVS with Darrell’s changes.

[NOT FOR REDISTRIBUTION]
I’ve created CVS snapshots available at http://www.libsdl.org/cvs/
SDL_image-1.2.2.tar.gz
SDL_mixer-1.2.3.tar.gz
SDL_net-1.2.4.tar.gz
SDL_ttf-2.0.5.tar.gz

Please don’t redistribute these files, since they are not packaged
for release.

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment> On Sunday, February 24, 2002, at 11:24 PM, Randall Leeds wrote:

Thanks Sam! This will help me in my development efforts
a lot!

Thank you too Darrell!

Dave>

From: Sam Lantinga
Date: 2002/02/26 Tue AM 09:35:13 EST
To: sdl at libsdl.org
Subject: Re: [SDL] OSX progress [potential BUG in SDL-devel package for OS X]

On Sunday, February 24, 2002, at 11:24 PM, Randall Leeds wrote:

My SDL_image install ended up in /Developer/Documentation/SDL,
try looking there. Is there a reason it ended up there?

The old installers are broken. The new ones (not yet in CVS) fix this.

I’ve updated the PBProjects in CVS with Darrell’s changes.

[NOT FOR REDISTRIBUTION]
I’ve created CVS snapshots available at http://www.libsdl.org/cvs/
SDL_image-1.2.2.tar.gz
SDL_mixer-1.2.3.tar.gz
SDL_net-1.2.4.tar.gz
SDL_ttf-2.0.5.tar.gz

Please don’t redistribute these files, since they are not packaged
for release.

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl