public inbox for cygwin-apps-cvs@sourceware.org help / color / mirror / Atom feed
From: jturney@sourceware.org To: cygwin-apps-cvs@sourceware.org Subject: [cygwin-apps htdocs - The cygwin-apps website files] branch master, updated. ff1b531cdc574fec12b5afaa784dc3ce41f63ca9 Date: Tue, 30 Jan 2018 20:03:00 -0000 [thread overview] Message-ID: <20180130200355.105537.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/apps-htdocs.git;h=ff1b531cdc574fec12b5afaa784dc3ce41f63ca9 commit ff1b531cdc574fec12b5afaa784dc3ce41f63ca9 Author: Jon Turney <jon.turney@dronecode.org.uk> Date: Mon Jan 29 18:20:15 2018 +0000 Document additional syntax supported by setup >=2.885 https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/apps-htdocs.git;h=e50c26c962a4b482bedb1ab636c0b0fdc9b01182 commit e50c26c962a4b482bedb1ab636c0b0fdc9b01182 Author: Jon Turney <jon.turney@dronecode.org.uk> Date: Mon Jan 29 18:12:33 2018 +0000 Clarify who gets to use the release label 'cygwin' Diff: --- setup.ini.html | 17 +++++++++++------ 1 files changed, 11 insertions(+), 6 deletions(-) diff --git a/setup.ini.html b/setup.ini.html index cdb92e8..1b89b0b 100644 --- a/setup.ini.html +++ b/setup.ini.html @@ -58,7 +58,7 @@ operate correctly on a <tt>setup.ini</tt> file to do so without warnings.</p> <p><tt>release: text</tt><p> <p>A label for the package set. The label <tt>cygwin</tt> is reserved for use -by Cygwin.</p> +by cygwin.com</p> <p><tt>arch: x86|x86_64</tt><p> <p>The processor architecture this package set is built for.</p> @@ -95,6 +95,10 @@ installed.</p> <p>Indicates a list of packages that this package needs at runtime in order to function correctly. Multiple packages should be separated by a space.</p> +<p><tt>replace-versions:<i>version[ version...]</i></tt><p> +<p>Optional. This is a list of withdrawn versions, which, if installed, should +be replaced with the curr: version, even if it is lower.</p> + <h4>Version description</h4> <p> @@ -147,15 +151,16 @@ for the current package version. i.e. for package foo-dev, one might have "Source: foo-src" to indicate that the source package for foo-dev is foo-src. This entry should not be used in conjunction with the "source:" entry.</p> -<h4>Note: The following directives are not fully implemented yet.</h4> - -<p><tt>Depends: <i>version-relations</i></tt></p> +<p><tt>depends2: <i>version-relations</i></tt></p> <p>This is a more sophisticated version of <tt>requires:</tt>, allowing the -specification of version relationships.</p> +specification of version relationships. <tt>depends:</tt> is a synonym +for <tt>depends2:</tt>.</p> -<p><tt>Obsoletes: <i>version-relations</i></tt></p> +<p><tt>obsoletes: <i>version-relations</i></tt></p> <p>Indicates packages this package obsoletes.</p> +<h4>Note: The following directives are not fully implemented yet.</h4> + <p><tt>Build-Depends: <i>version-relations</i></i></tt></p> <p>Indicates the binary packages required to build the source package.</p>
reply other threads:[~2018-01-30 20:03 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180130200355.105537.qmail@sourceware.org \ --to=jturney@sourceware.org \ --cc=cygwin-apps-cvs@sourceware.org \ /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: linkBe 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).