public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Add initial support for SOURCE_DATE_EPOCH
Date: Wed, 23 Aug 2023 20:45:20 -0600	[thread overview]
Message-ID: <2aa9ce84-9cab-8c77-f1fd-c7c9142af233@Shaw.ca> (raw)
In-Reply-To: <d9b666aa-82c7-4143-26ca-8bf87c379a78@t-online.de>

On 2023-08-23 11:39, Christian Franke via Cygwin-apps wrote:
> A small step towards reproducible packaging...
> 
> Currently only tested with upcoming smartmontools package - contains only exe, 
> man, doc files (no dll, lib, ...). Multiple cygport runs produce binary 
> identical distribution tarballs if SOURCE_DATE_EPOCH (from the past) is 
> specified in the cygport file.

What format is this variable?
Would be best to use some ISO format e.g.

	%Y-%m-%dT%H:%M:%SZ	or
	%Y-%m-%dT%H:%M:%S	[local]

that is human readable and can be used by all POSIX command options
[e.g. see touch(1p) -d] that accept date-time stamps.

Could do with docs and NEWS entries for new variables, otherwise packagers do 
not know it exists, and how to use it e.g.

#****f* Information/BUILD_REQUIRES
#  SYNOPSIS
#  BUILD_REQUIRES="ATOM [ATOM] ..."
#  DESCRIPTION
#  A single-line strings containing a list of packages on which this source
#  package depends at build-time. This will be added to the build-depends:
#  field of the auto-generated -src.hint file.
#  NOTES
#  * Unlike REQUIRES, there is no auto-detection of build-time requirements.
#  * Any newlines in this variable must be escaped.
#  * Unlike the deprecated DEPEND variable, only actual package names, or
#    atoms that are listed PROVIDES of other packages, may be used in this
#    variable.
#****

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry


  reply	other threads:[~2023-08-24  2:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 17:39 Christian Franke
2023-08-24  2:45 ` Brian Inglis [this message]
2023-08-24  6:09   ` Christian Franke
2023-08-24  6:27     ` ASSI
2023-08-24  6:36       ` Christian Franke
2023-08-28 15:12 ` Christian Franke
2023-08-28 15:51   ` ASSI
2023-08-29  8:52     ` Christian Franke
2023-10-29 16:05   ` Jon Turney
2023-10-30 17:43     ` Christian Franke

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2aa9ce84-9cab-8c77-f1fd-c7c9142af233@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --cc=cygwin-apps@cygwin.com \
    /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).