From: Akim Demaille <akim@lrde.epita.fr>
To: Bruno Haible <bruno@clisp.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: backup-rename: update dependencies
Date: Mon, 14 Jan 2019 19:43:26 +0100 [thread overview]
Message-ID: <20800E24-D18B-4FDB-BCA4-7359C355F763@lrde.epita.fr> (raw)
In-Reply-To: <5375456.dSRKqpzxv4@omega>
> Le 14 janv. 2019 à 00:42, Bruno Haible <bruno@clisp.org> a écrit :
>
> Hi Akim,
>
>> I think that it's more than this.
>
> Indeed!
>
>> * modules/backup-rename (Depends-on): It now depends on opendirat
>> instead of opendir. It also uses stdbool, and xalloc-oversized.
>> But no longer dirfd.
>> * modules/backupfile (Depends-on): Add xalloc-oversized.
>
> Typo in ChangeLog entry: s/stdbool/stdint/. Other than that, the patch
> looks fine. Thanks!
Fixed and installed.
>> It seems quite difficult to track these dependencies.
>> Can nothing be automated there?
>
> $ ./gnulib-tool --test --without-tests
>
> is a way to check whether the dependencies are complete, at least
> regarding the platform on which you are running this.
>
> When 'xalloc-oversized' is present through indirect dependencies, we
> don't have an automated way to find that it's missing as a direct
> dependency in the module description.
>
> For POSIX function modules, we do have a mechanism:
> https://www.gnu.org/software/gnulib/manual/html_node/Finding-POSIX-substitutes.html
Thanks a lot for these pointers!
prev parent reply other threads:[~2019-01-14 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 10:30 backup-rename: update dependencies Akim Demaille
2019-01-13 12:31 ` Bruno Haible
2019-01-13 18:45 ` Akim Demaille
2019-01-13 20:40 ` Paul Eggert
2019-01-13 23:42 ` Bruno Haible
2019-01-14 18:43 ` Akim Demaille [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20800E24-D18B-4FDB-BCA4-7359C355F763@lrde.epita.fr \
--to=akim@lrde.epita.fr \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).