Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Aug 1996 15:01:27 -0700 (PDT)
From:      Satoshi Asami <asami>
To:        andreas@klemm.gtn.com, ports@freebsd.org
Cc:        matt@bdd.net
Subject:   Re: Port Question : ghostscript-4.01 (fwd)
Message-ID:  <199608302201.PAA29566@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
 * Another thing we can do is to check and print out a warning if it doesn't
 * look friendly.  This is easy, and I posted a patch here a while ago
 * (sorry I can't get to my mail archive now).  I can commit it if that's
 * what people want.

Actually, I had already committed that patch. ;)

===
Date: Sun, 18 Aug 1996 03:53:19 -0700 (PDT)
From: Satoshi Asami <asami@freefall.freebsd.org>
To: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org,
        cvs-share@freefall.freebsd.org
Subject: cvs commit:  src/share/mk bsd.port.mk

asami       96/08/18 03:53:18

  Modified:    share/mk  bsd.port.mk
  Log:
  (1) Use INSTALL_PROGRAM where we attempt to pass this command line
      to configure.

  (2) Gently warn user for non-0022 umasks.

  Submitted by: "David E. O'Brien" <obrien@Nuxi.cs.ucdavis.edu> (1)

  Revision  Changes    Path
  1.221     +7 -2      src/share/mk/bsd.port.mk
===

Well, so there it is.  If that's too gentle, we can change it.

Actually, there is a problem when the sysadmin changes the umask only
during installation (the check is done from do-install), and
files generated during earlier steps (like .elc files for emacs)
end up being generated mode 640 and copied over with that permission.

But we can't cover every base.  And if people complain about bsd.port.mk
and pkg_add, they should also complain about cp. :)

Satoshi



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