Bug 7090 - Need chmod on directories created with "make install"
Summary: Need chmod on directories created with "make install"
Status: RESOLVED NOTOURBUG
Alias: None
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: 1.0.4
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-01 12:07 UTC by Bryan Raney
Modified: 2006-06-14 07:17 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Bryan Raney 2006-06-01 12:07:32 UTC
Overview Description:

After running "make install" on the Cairo 1.0.4 release tarball, I found that
some of the directories it created did not have proper permissions for "other
users".  I had to perform these commands manually to be able to use Cairo
(specfically, to compile cairomm 0.6.0) or view documentation as a regular user:

chmod o+r+x /usr/local/lib/pkgconfig
chmod o+r+x /usr/local/include/cairo
chmod o+r+x /usr/local/share/gtk-doc/
chmod o+r+x /usr/local/share/gtk-doc/html

Steps to Reproduce:

1. wget http://cairographics.org/releases/cairo-1.0.4.tar.gz
2. tar xzf cairo-1.0.4.tar.gz
3. cd cairo-1.0.4
4. ./configure
5. make
6. make check
7. (as root) make install

Actual Results:

Make created the following directories during the installation:

/usr/local/include/cairo
/usr/local/lib/pkgconfig
/usr/local/share/gtk-doc
/usr/local/share/gtk-doc/html

All of them had permissions "drwxr-x---" (0750).

Expected Results:

New directories would have permissions of "drwxr-xr-x" (0755).

Build Date & Platform:

Tarball of cairo-1.0.4 ; built under Fedora Core 4 with all available package
updates.

Additional Builds and Platforms:

Unknown.

Additional Information:

The individual files created by "make install" seem to have proper permissions;
just the new directories had problems.

My regular user account and my root account both use a umask of "0027", while
the default is "0022".  Perhaps this had an effect on the installation process.
Comment 1 Behdad Esfahbod 2006-06-14 00:55:20 UTC
If you have set umask to 0027, that's what you get.  It's simply wrong to not
follow that.  And it's all up to automake to create those directories anyway, we
are not going to chmod it.  If you still feel like this is a bug, you should
report to automake.
Comment 2 Bryan Raney 2006-06-14 07:17:16 UTC
(In reply to comment #1)
> If you have set umask to 0027, that's what you get.  It's simply wrong to not
> follow that.  And it's all up to automake to create those directories anyway, we
> are not going to chmod it.  If you still feel like this is a bug, you should
> report to automake.

OK, thanks for taking a look.  I'll check out automake's bugzilla.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.