[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Please include the local gnulib modules in releases
From: |
Bruno Haible |
Subject: |
Re: Please include the local gnulib modules in releases |
Date: |
Tue, 15 Oct 2024 15:51:10 +0200 |
Michael Pratt wrote:
> > > What's needed is just the "modules" files which are missing
> >
> >
> > No, the gl/lib/ and gl/tests/ subdirectories are input to gnulib-tool as
> > well.
> > Not only gl/modules/.
> >
> > And you should list the files to add to the tarball, not directories.
>
>
> To clarify, I was referring to the fact that the gl/lib/ and gl/tests/
> files do exist in the tarball already, but in the lib and tests directories.
> I used the word "needed" to refer to the content
> that was strictly not already there in any form.
> Then, with some manual copying, the results would be the same,
> but otherwise, the data doesn't exist in the contents.
If "some manual copying" is needed, before running gnulib-tool from an
extracted tarball, the tarball did not contain what we call the "source code".
> I also imagine a possible feature (or option? or when --force is passed)
> for gnulib-tool to look for the files in the lib and tests directories
> for whatever is missing in the local_dir/lib and local_dir/tests directories,
> so that, for example, if only gl/modules files were added to EXTRA_DIST,
> gnulib-tool can assume that the files of the modules were installed already.
It is generally a good idea for a build tool to be clear what is input and
what is output.
It is generally a bad idea for a build tool to mix input and output in such
a way that a single file is both input and output.
Bruno