On Mon, Jul 18, 2022 at 10:22 AM Bruno Haible wrote:
>
> Jeffrey Walton wrote:
> > I believe MacOS maps /etc and /tmp to a private area for the user.
> > They are not world readable/writable. I believe Apple did it for
> > hardening.
> >
> > Here's from a MacOS X 10.5 machine I have:
> >
> > $
Jeffrey Walton wrote:
> I believe MacOS maps /etc and /tmp to a private area for the user.
> They are not world readable/writable. I believe Apple did it for
> hardening.
>
> Here's from a MacOS X 10.5 machine I have:
>
> $ ls -l /etc /tmp
> lrwxr-xr-x@ 1 root wheel 11 Feb 10 2015 /etc
On Mon, Jul 18, 2022 at 8:18 AM Edward Welbourne wrote:
>
> Alejandro Colomar (Monday, July 18, 2022 14:07)
> > MacOS seems to be setting TMPDIR (or at least some script run at
> > startup seems to be setting it in my system), and it's set to something
> > really weird that I don't trust will exis
Hi Eddy,
On 7/18/22 14:17, Edward Welbourne wrote:
Alejandro Colomar (Monday, July 18, 2022 14:07)
MacOS seems to be setting TMPDIR (or at least some script run at
startup seems to be setting it in my system), and it's set to something
really weird that I don't trust will exist after reboot.
Hi Alfred,
On 7/18/22 13:51, Alfred M. Szmidt wrote:
I'm improving a Makefile for a project which uses [/usr/local]/var/lib
and [/usr/local]/tmp. I see there's no standard in the GNU coding
standards for directory variables.
I used the following:
tmpdir := $(prefix)/tmp
Alejandro Colomar (Monday, July 18, 2022 14:07)
> MacOS seems to be setting TMPDIR (or at least some script run at
> startup seems to be setting it in my system), and it's set to something
> really weird that I don't trust will exist after reboot.
Then I think the way you're using tmpdir doesn't
Hi Alfred,
On 7/18/22 13:51, Alfred M. Szmidt wrote:
So you're saying that "should normally be" doesn't mean the "the
default value should normally be", but rather that "commonly,
people use".
Right, the _default_ value depends on _your_ system. On some systems,
it is one thing, an
On 7/18/22 13:41, Bruno Haible wrote:
Alejandro Colomar wrote:
I used the following:
tmpdir := $(prefix)/tmp
Writing it like this has two drawbacks:
1) The user cannot force a specific temporary directory by setting
the TMPDIR environment variable. This may be blocking if the
I'm improving a Makefile for a project which uses [/usr/local]/var/lib
and [/usr/local]/tmp. I see there's no standard in the GNU coding
standards for directory variables.
I used the following:
tmpdir := $(prefix)/tmp
libstatedir := $(localstatedir)/lib
I developed the na
So you're saying that "should normally be" doesn't mean the "the
default value should normally be", but rather that "commonly,
people use".
Right, the _default_ value depends on _your_ system. On some systems,
it is one thing, and on other it is something else.
Which is why "you" (you i
Hi Alejandro,
I think the source of the confusion is that "Should normally be" and how
you should write a default value don't match up because it is normal to
use non-default values.
So systems are commonly set up with localstatedir=/usr/var and
runstatedir=/var/run, despite t
Alejandro Colomar wrote:
> I used the following:
>
> tmpdir := $(prefix)/tmp
Writing it like this has two drawbacks:
1) The user cannot force a specific temporary directory by setting
the TMPDIR environment variable. This may be blocking if the
default temporary directory has not enou
Hi,
I'm improving a Makefile for a project which uses [/usr/local]/var/lib
and [/usr/local]/tmp. I see there's no standard in the GNU coding
standards for directory variables.
I used the following:
tmpdir := $(prefix)/tmp
libstatedir := $(localstatedir)/lib
I developed the name $libstatedi
Hi Edward,
On 7/18/22 12:25, Edward Welbourne wrote:
Hi Alejandro,
I think the source of the confusion is that "Should normally be" and how
you should write a default value don't match up because it is normal to
use non-default values.
So systems are commonly set up with localstatedir=/usr/var
Hi Alejandro,
I think the source of the confusion is that "Should normally be" and how
you should write a default value don't match up because it is normal to
use non-default values.
So systems are commonly set up with localstatedir=/usr/var and
runstatedir=/var/run, despite the fact that their d
On 7/18/22 11:17, Alfred M. Szmidt wrote:
Oh, there _is_ a bug. Compare what the documentation says, with a bit
of variable expansion that I did to show the bug (between parentheses):
Documentation says:
$prefix
Should normally be */usr/local*
$localstate
Oh, there _is_ a bug. Compare what the documentation says, with a bit
of variable expansion that I did to show the bug (between parentheses):
Documentation says:
$prefix
Should normally be */usr/local*
$localstatedir
Should normally be */usr/local/var*
Hi Alfred,
On 7/17/22 16:18, Alfred M. Szmidt wrote:
How can $localstatedir be $prefix/var and at the same time $runstatedir
be /var/run (notice no prefix) if it is defined as $localstatedir/run.
Because prefix is normally /usr, and it was/is common to use /usr/var
for exactly that purp
18 matches
Mail list logo
