Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3
Date: Tue, 3 Apr 2018 00:29:13 -0300 (BRT)	[thread overview]
Message-ID: <1509094450.1293032.1522726153234.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20180402112650.1e7a17a6@windsurf>

> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: "buildroot" <buildroot@buildroot.org>, "Romain Naour" <romain.naour@gmail.com>
> Sent: Monday, April 2, 2018 6:26:50 AM
> Subject: Re: [Buildroot] [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3

> Hello,
> 
> On Fri, 15 Dec 2017 13:38:29 -0200, Carlos Santos wrote:
> 
>> +# This package is really annoying since the archive name doesn't contain the
>> +# version. Use a small trick to save it with a better name.
>> +define IQVLINUX_DOWNLOAD
>> +	$(EXTRA_ENV) $(DL_WRAPPER) -b wget \
>> +		-o $(DL_DIR)/$(IQVLINUX_SOURCE) \
>> +		-H $(PKGDIR)/$($(PKG)_RAWNAME).hash \
>> +		-- \
>> +		$(IQVLINUX_SITE)/iqvlinux.tar.gz
>> +endef
>> +
>> +IQVLINUX_PRE_DOWNLOAD_HOOKS = IQVLINUX_DOWNLOAD
> 
> So instead of this, I've added an iqvlinux-1.2.0.3.tar.gz tarball on
> sources.buildroot.net, and just kept iqvlinux download first from
> SourceForge (which fails with a 404), and then fall back to
> sources.buildroot.net.
> 
> Accessing directly the download helper is not a good idea. The download
> helpers are internal, and they are being changed by Maxime/Yann patch
> series introducing Git caching, so we really don't want packages to
> mess up with the download internals.
> 
> It would be good if you could reply on the bug report upstream, explain
> why and how you use iqvlinux, and convince them to fix their tarball
> name.

I posted a reply there. Meanwhile they released version 1.2.0.8 and
named it "iqvlinux.tar.gz". :-(

> I've applied both patches to master, after doing the change explained
> above. Thanks!

Thanks

-- 
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent 
success of having your words and actions judged by your reputation, 
rather than the other way about.? ? Christopher Hitchens

      reply	other threads:[~2018-04-03  3:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 15:38 [Buildroot] [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3 Carlos Santos
2017-12-15 15:38 ` [Buildroot] [PATCH v2 2/2] iqvlinux: add patch to support Linux kernel 4.12 and later Carlos Santos
2017-12-15 15:38   ` [Buildroot] FW: " Kees van Unen
2017-12-15 15:38 ` [Buildroot] FW: [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3 Kees van Unen
2017-12-16 14:50 ` [Buildroot] " Thomas Petazzoni
2017-12-16 19:03   ` Carlos Santos
2017-12-16 19:53     ` Carlos Santos
2017-12-17  4:05       ` Thomas Petazzoni
2018-01-09  9:56         ` Thomas Petazzoni
2018-01-10  1:56           ` Carlos Santos
2018-02-14 11:38             ` Carlos Santos
2018-02-14 12:38               ` Thomas Petazzoni
2018-02-14 19:37                 ` Carlos Santos
2018-02-14 19:46                   ` Thomas Petazzoni
2018-04-01 22:37 ` Thomas Petazzoni
2018-04-03  3:29   ` Carlos Santos
2018-04-02  9:26 ` Thomas Petazzoni
2018-04-03  3:29   ` Carlos Santos [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=1509094450.1293032.1522726153234.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox