public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Updated: neomutt-2019-10-25-1
Date: Sat, 26 Oct 2019 09:48:00 -0000	[thread overview]
Message-ID: <87d0ejj0s7.fsf@Rainer.invalid> (raw)
In-Reply-To: <0E12A417-02C3-4940-9A1F-3D85511B1601@gmail.com> (Federico	Kircheis's message of "Sat, 26 Oct 2019 05:33:13 +0000")

Federico Kircheis writes:
> The new neomutt version uses this version number, how do I lose the
> extra dashes?

The files are named like the tag in Git and they changed that format
with the last release it seems.

> Rename the tar package after the download? Remove them from the build folder before the upload?
> Are there some reccomended practices?

Something along these lines should do it:

--8<---------------cut here---------------start------------->8---
TAG="2019-10-25"
SRC_URI="
  https://github.com/neomutt/neomutt/archive/${TAG}.tar.gz#/${P}.tar.gz
  https://github.com/neomutt/neomutt/archive/${TAG}tar.gz.sig#/${P}.tar.gz.sig
  "
SRC_DIR="neomutt-${TAG}"
--8<---------------cut here---------------end--------------->8---

Another way would probably be to have ORIG_PN and NAME set differently,
but I haven't used that yet.

Also, you should send the announcement to the announcement mailing list,
not cygwin-apps.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2019-10-26  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 18:13 Federico Kircheis
2019-10-25 18:55 ` Achim Gratz
2019-10-26  5:33   ` Federico Kircheis
2019-10-26  9:48     ` ASSI [this message]
2019-10-26 13:04       ` Federico Kircheis

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=87d0ejj0s7.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).