All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/zip: adjust the version to 3.0
Date: Mon, 29 Jul 2019 09:27:09 +0200	[thread overview]
Message-ID: <20190729092709.3661757d@windsurf> (raw)
In-Reply-To: <20190620134809.10007-1-thomas.petazzoni@bootlin.com>

On Thu, 20 Jun 2019 15:48:09 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> According to the project homepage at
> http://infozip.sourceforge.net/Zip.html, the version is really named
> 3.0. This is also how it's called inside the zip30.ann file in the
> source code, which says "We have posted Zip 3.0, July 5th 2008".
> 
> So the fact that the tarball is named zip30.tgz is just because
> upstream wanted to avoid having two dots (perhaps by habit of the old
> DOS 8.3 file name limitation ?).
> 
> The version is also named "3.0" in the SourceForge RSS at [0] that
> release-monitoring.org is using for this package [1]. Therefore, by
> using "3.0" as the version, we will match the version known by
> release-monitoring.org.
> 
> Of course the tarball name is still zip30.tgz so we tweak the
> ZIP_VERSION value appropriately.
> 
> [0] https://sourceforge.net/projects/infozip/rss?path=/
> [1] https://release-monitoring.org/project/10080/
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
>  package/zip/zip.mk | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-07-29  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 13:48 [Buildroot] [PATCH] package/zip: adjust the version to 3.0 Thomas Petazzoni
2019-07-29  7:27 ` Thomas Petazzoni [this message]

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=20190729092709.3661757d@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.