"Vin Shelton" <acs(a)xemacs.org> writes:
On 3/6/06, Ville Skyttä <scop(a)xemacs.org> wrote:
> On Mon, 2006-03-06 at 13:22 -0500, Vin Shelton wrote:
>
> > I'm observing the following error in 'make bindist':
> >
> > cp -af
/usr/local/build/xemacs-packages-2006-03-06/xemacs-packages/jde/plugins/README.txt
> > /home/vshelton/tmp/staging/etc/jde/plugins
> > cp: cannot stat
> >
`/usr/local/build/xemacs-packages-2006-03-06/xemacs-packages/jde/plugins/README.txt':
> > No such file or directory
> > make: *** [binkit-1] Error 1
> >
> > creating an empty jde/plugins/README.txt allows the build to continue.
>
> Hm, I cannot reproduce. There is a
> xemacs-packages/jde/plugins/README.txt in CVS [0]. Could you verify
> that your packages CVS checkout is fully up to date?
>
> [0]
http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/jde/plu...
>
>
>
cvs update would not get me the plugins directory:
ls jde
CVS ChangeLog Makefile doc etc java lisp package-info.in
but a clean checkout did, in fact create the plugins directory and the
README.txt file.
Curious....
Hi Vin,
I include
`-P'
Prune empty directories. See *Note Moving directories::.
and
`-d'
Create any directories that exist in the repository if they're
missing from the working directory. Normally, `update' acts only
on directories and files that were already enrolled in your
working directory.
This is useful for updating directories that were created in the
repository since the initial checkout; but it has an unfortunate
side effect. If you deliberately avoided certain directories in
the repository when you created your working directory (either
through use of a module name or by listing explicitly the files
and directories you wanted on the command line), then updating
with `-d' will create those directories, which may not be what you
want.
in my cvs update options to pick up changes in directory structure.
That should help.
Adrian
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/