Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Aug 1996 08:36:11 -0700 (PDT)
From:      "David E. O'Brien" <obrien@Nuxi.cs.ucdavis.edu>
To:        freebsd-ports@freebsd.org (FreeBSD ports list)
Subject:   Re: ports/print/ghostscript4
Message-ID:  <199608011536.IAA09853@relay.nuxi.com>
In-Reply-To: <199608010450.VAA01193@baloon.mimi.com> from Satoshi Asami at "Jul 31, 96 09:50:30 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
>  * They should!  Over the weekend I installed 2.1.5-R and 82 megs of
>  * packages.  With my fascist root umask, over half the ports were installed
>  * such that mear mortals could not use them.  Quite annoying.
>  * 
>  * Could bsd.port.mk set a "umask 022"???
> 
> Hey, if you are talking about packages, bsd.port.mk is not going to
> help! ;)

I kinda expected that if an explicit "umask 022" was put in bsd.port.mk
that the resulting +CONTENTS file would have approapiate "@mode" lines.
I guess it shows I don't know too much about the package transformation
process from a port and how all those "@" lines get in there.

My qualm wasn't as much with the resulting permissions when I build a
port manually.  I figure if I went to that much trouble, then I should
have the control to have more fascist file permisssions.  But, I expected
that when I install a Package, that it is installed with the permissions
of the files it was build from.  Correct me if I am wrong, but in order
to create a package, you must ``make install'' a port first.  The
resulting package is just a tarball of the installed files, and some
magic to produce the +CONTENTS and +MTREE_DIRS files.  I assume that you
are using a umask of 022 when you built the offical packages.  (yea I
know what "assume" stands for :-))
 
> I guess we can add a umask() call to pkg_add, but I'm not sure if
> Jordan agrees it's a good thing.  

Not an explicit umask() call, but just presurve the permissions on the
files in the pre-compiled package.

> If you have "umask 027" or some such in your root .cshrc, it means you
> want to create files with that permission

There could be an option to pkg_add that would override the permissions
in the package when adding.  Yea, I know, "yuck!  not yet another
option".

Just a thought,
-- David



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608011536.IAA09853>