Amanda Waite wrote:
> Re: RubyGems 1.3.1 update to Ruby packages:
>
> With Ruby and RubyGems 0.9.4 we included all of the RubyGems
> documentation directories in ${SRC}/TargetDirs. With the RubyGems 1.3.1
> update, we use the RubyGems install script to install directly to the
> appropriate directory in the proto area and the installer kindly removes
> everything that's there first, which basically is the RubyGems doc
> structure created from TargetDirs.
>
> There are hundreds of directories (244) and it would be a trial to have
> to install RubyGems to a temporary directory and then install all of the
> files through the install-sfw script. Is it ok to let the RubyGems
> installer create the directory structure itself and leave all of the
> entries out of TargetDirs?
it depends.
I wasn't there when Targetdirs was created in concept, but I look at
it as a way to create directories so that all the sub-Makefiles don't
have to. It isn't that useful if only one thing would create them
anyway, but if more than one thing might want to make sure
/usr/share/lib/foo exists so it can put something in it, having
it in Targetdirs makes sure that we only have to create it in
one place, and it gets created with the right permissions and
(in the old days) owner/group, avoiding parallel build races where
several things try to create it and might either get something wrong
or even fail and break the build.
If rubygems is creating a private directory hierarchy and nothing else
would ever want to stuff things in there then sure it can do it outside
Targetdirs.
Mike
