Re: publish PGP-signed git bundles of gnulib?

Bruno Haible writes: > Hi Simon, > >> >> 1) Add a section to the gnulib manual describing what gnulib publish at >> >> ftp.gnu.org and that it is a Git bundle for archival purposes. >> >> I've pushed the patch below to start this, what do you all think? > > I would change ftp:// -> https:// (bec

Re: publish PGP-signed git bundles of gnulib?

Hi Simon, > >> 1) Add a section to the gnulib manual describing what gnulib publish at > >> ftp.gnu.org and that it is a Git bundle for archival purposes. > > I've pushed the patch below to start this, what do you all think? I would change ftp:// -> https:// (because browsers like Firefox no lon

Re: publish PGP-signed git bundles of gnulib?

ulib at @url{ftp://ftp.gnu.org/gnu/gnulib/}. These may be useful if +Savannah happens to be offline or if you want to have a GnuPG signed +confirmation of the Gnulib content. + +The files are named like @code{gnulib-MMDD.bundle}, for example +@code{gnulib-20250303.bundle}, where @code{MMD

Re: vasprintf-gnu wants me to #include "vasprintf.h" but it does not exist

Hi, Vivien Kraus wrote: > I want asprintf. The manual page tells me it can be provided by > vasprintf-gnu. However, if I import the vasprintf-gnu module, it tells > me to add: > #include "vasprintf.h" > > (like vasprintf-posix, but vasprintf tells me to just include stdio.h) > > But this file

vasprintf-gnu wants me to #include "vasprintf.h" but it does not exist

Dear Gnulib developers, I want asprintf. The manual page tells me it can be provided by vasprintf-gnu. However, if I import the vasprintf-gnu module, it tells me to add: #include "vasprintf.h" (like vasprintf-posix, but vasprintf tells me to just include stdio.h) But this file does not seem to

Re: tar --mtime

On 2025-03-03 03:54, Bruno Haible via Gnulib discussion list wrote: I don't think we have any users on HP-UX any more, for several years already. still seems to be active. It has a 64-bit Itanium 2 copy of Coreutils 9.6, released in January. Insta

Re: tar --mtime

Bruno Haible via Gnulib discussion list writes: >> > - a POSIX file system (not the Haiku file system, which assigns slightly >> > different mtimes at random when the tarball is unpacked). >> >> There is the idea to store modification times of files in a text file >> suitable for parsing a

Re: tar --mtime

Simon Josefsson wrote: > > - a 'make' program that considers equal time stamps as "up-to-date" > > (a condition fulfilled by all 'make' programs except HP-UX make), > > Yes you are right. But for users, advice should be practical -- is > there any reasonable way to solve the problem on HP-U

Re: tar --mtime

Bruno Haible writes: > Simon Josefsson wrote: >> Personally I use tar --mtime to the latest git commit time instead of >> the complexity of the vc-mtime approach. I've done two software >> releases with this approach (libtasn1, inetutils) and no reports of >> problems so far, but I'm open to the

Re: tar --mtime

Simon Josefsson wrote: > Personally I use tar --mtime to the latest git commit time instead of > the complexity of the vc-mtime approach. I've done two software > releases with this approach (libtasn1, inetutils) and no reports of > problems so far, but I'm open to the idea that this is a too prim

Re: new module 'vc-mtime'

Vivien Kraus writes: > Hello, > > Le lundi 24 février 2025 à 19:10 +0100, Bruno Haible via Gnulib > discussion list a écrit : >> The "version-controlled modification time" vc_mtime(F) of a file F >>    is defined as: >> - If F is under version control and not modified locally: >>    the