[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Distcheck: cannot create regular file

From: Bruce Korb
Subject: Re: Distcheck: cannot create regular file
Date: Sat, 15 Feb 2003 14:30:48 -0800

Alexandre Duret-Lutz wrote:
>  Bruce> cp: cannot create regular file \
>  Bruce> `blocksort-1.4.2/libopts/.deps/save.Plo': Permission denied
> Simply don't distribute these files.

Distributing files marked read-only or in read-only directories
really ought not cause a distribution failure.  It is far simpler
to just say, "distribute the contents of the libopts directory".

The reason this is inconvenient is that from my client's point
of view (blocksort developer's point of view), they don't want
to know what goes into the libopts subdirectory.  So, I'll
construct a redistribution list file containing something
like this (the contents of my "tear-off" library):

> $ cat libopts/dist.list
>     libopts/COPYING.lgpl  libopts/COPYING.mbsd  libopts/  \
>     libopts/README        libopts/autoopts.c    libopts/autoopts.h  \
>     libopts/boolean.c     libopts/compat        libopts/dist.list  \
>     libopts/enumeration.c libopts/libopts.m4    libopts/numeric.c  \
>     libopts/options.h     libopts/pgusage.c     libopts/restore.c  \
>     libopts/save.c        libopts/stack.c       libopts/streqv.h  \
>     libopts/streqvcmp.c   libopts/usage.c       libopts/version.c

'course, that has a drawback, too:

> $ make distcheck
> [[...]]
> configure: creating ./config.status
> config.status: creating libopts/Makefile
> config.status: error: cannot find input file: libopts/
> make: *** [distcheck] Error 1

So, "libopts/" got created when blocksort got bootstrapped,
but wasn't distributed.  I've added "libopts/" to this list
manually on the assumption that the redistributor will create this file.
If the bootstrap process creates any other files, the bootstrap-per
will have to know to add them to the list.

It seems to work now.  Thanks, Alexandre.  This is a really gnarly
little twisty hassle, but I think I've simplified the issue as much
as I know how.  Here's the README for how to incorporate a tear-off
library into a client distribution:

I hope it makes sense.  Feedback appreciated.
One person tried and failed with the previous version.  :-(

Cheers - Bruce

reply via email to

[Prev in Thread] Current Thread [Next in Thread]