Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permission for doc/examples with sudo make install #161

Open
Misairu-G opened this issue Jul 1, 2018 · 2 comments
Open

Permission for doc/examples with sudo make install #161

Misairu-G opened this issue Jul 1, 2018 · 2 comments

Comments

@Misairu-G
Copy link

Hi, it looks like make install set everything inside /usr/share/doc/check to 0600 and 0700. If anyone try install it with sudo make install, those examples will be unaccessible.

I think 0644 and 0755 would be a better option.

@brarcher
Copy link
Contributor

brarcher commented Jul 1, 2018

Looking through the configure script and Makefile.am files, I do not see where the permissions are being set, especially to 600 or 700. If you happen to know what is going on in this case, let me know.

@jflopezfernandez
Copy link
Collaborator

If you run make -n install after building, you can see all of the commands that make would run if you ran it without the -n flag.

list='ChangeLog NEWS README COPYING.LESSER'; test -n "/usr/local/share/doc/check" || list=; \
if test -n "$list"; then \
  echo " /usr/bin/mkdir -p '/usr/local/share/doc/check'"; \
  /usr/bin/mkdir -p "/usr/local/share/doc/check" || exit 1; \
fi; \
for p in $list; do \
  if test -f "$p"; then d=; else d="./"; fi; \
  echo "$d$p"; \
done | sed '$!N;$!N;$!N;$!N;$!N;$!N;$!N;s/\n/ /g' | sed '$!N;$!N;$!N;$!N;s/\n/ /g' | \
while read files; do \
  echo " /usr/bin/install -c -m 644 $files '/usr/local/share/doc/check'"; \
  /usr/bin/install -c -m 644 $files "/usr/local/share/doc/check" || exit $?; \
done

With that being said, everything looks to be in order here. The install commands run by both Arch Linux and FreeBSD are using the default of 0644 for files.

Is it possible you had a more restrictive umask(1) setting set when you ran the command?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants