[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: make distcheck creates directory that I don't have write permissions
Re: make distcheck creates directory that I don't have write permissions for - is this expected?
Sat, 5 Nov 2005 18:45:54 +0100
* Ed Hartnett wrote on Sat, Nov 05, 2005 at 03:39:21PM CET:
> I'm trying to get make distcheck working for my package, and I've
> noticed something that's a little inconvenient. When it unpacks my
> package, all the files are read-only, so that when I try and delete
> the directory, I get a bunch of permission denied errors.
> Is this expected behavior from make dist?
> Is this what the user see when he unpacks my package - a bunch of
> read-only files?
No. This happens only during 'make distcheck' but not during 'make
The readonly setting during distcheck is supposed to be a feature:
When you issue 'make distcheck', first the dist target is updated,
i.e., a tarball is created, then that is unpacked, then the unpacked
directory is made readonly, and a VPATH build (source tree != build
tree) is performed. The readonly source tree checks that your tarball
is self-contained, ie. does not update or create anything below the
In some situations, this might be too strict, but most of the time it
can be achieved by fixing the distribution. How does your specific
problem look like?