From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: 22242@debbugs.gnu.org
Subject: bug#22242: Help constructing source URL
Date: Sat, 26 Dec 2015 08:46:38 +0100 [thread overview]
Message-ID: <8760zl649t.fsf@elephly.net> (raw)
In-Reply-To: <20151226070559.GA11537@jasmine>
Leo Famulari <leo@famulari.name> writes:
> Our tinyproxy package needs to be updated to use the current source URL.
>
> The current URL is:
> https://download.banu.com/tinyproxy/1.8/tinyproxy-1.8.3.tar.gz
>
> I don't know how to abstract the "1.8" directory to account for other
> versions.
How about this:
(string-append "https://download.banu.com/tinyproxy/"
(version-major+minor version)
"/tinyproxy-" version ".tar.gz")
~~ Ricardo
next prev parent reply other threads:[~2015-12-26 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 7:05 bug#22242: Help constructing source URL Leo Famulari
2015-12-26 7:46 ` Ricardo Wurmus [this message]
2015-12-26 13:32 ` Andreas Enge
2015-12-26 16:48 ` Leo Famulari
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760zl649t.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=22242@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).