From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3
Date: Wed, 14 Feb 2018 20:46:55 +0100 [thread overview]
Message-ID: <20180214204655.3d13fc3f@windsurf.lan> (raw)
In-Reply-To: <1373112436.78108.1518637053844.JavaMail.zimbra@datacom.ind.br>
Hello,
+Yann in Cc.
On Wed, 14 Feb 2018 17:37:33 -0200 (BRST), Carlos Santos wrote:
> > From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> > To: "Carlos Santos" <casantos@datacom.ind.br>
> > Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>, "Romain Naour" <romain.naour@gmail.com>, "buildroot"
> > <buildroot@buildroot.org>
> > Sent: Wednesday, February 14, 2018 10:38:56 AM
> > Subject: Re: [Buildroot] [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3
>
> > Hello,
> >
> > On Wed, 14 Feb 2018 09:38:06 -0200 (BRST), Carlos Santos wrote:
> >
> >> >> In the end, did you get the chance to raise the issue of the tarball
> >> >> name with the upstream developers ?
> >> >
> >> > Thanks for reminding me of this issue. I just submitted a ticket:
> >> >
> >> > https://sourceforge.net/p/e1000/bugs/589/
> >>
> >> No love, so far. :-(
> >
> > I pinged on the bug report, just in case, but indeed, there isn't much
> > hope.
>
> So we cannot upgrade the package without some hack to like the one in
>
> https://patchwork.ozlabs.org/patch/849230/
>
> It works, but uses $(DL_WRAPPER), which should be opaque to recipes.
Either that, or we add explicit support for this in the package
infrastructure, but it's a bit annoying. Indeed, if you have several
files to download (in <pkg>_SOURCE, <pkg>_EXTRA_DOWNLOADS and
<pkg>_PATCH), specifying what destination file name should be used is a
bit tricky.
Yann, your thoughts ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-14 19:46 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 [this message]
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
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=20180214204655.3d13fc3f@windsurf.lan \
--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.