From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/mesa3d: bump to version 18.3.1
Date: Sat, 15 Dec 2018 14:40:23 +0100 [thread overview]
Message-ID: <20181215134023.GG2625@scaer> (raw)
In-Reply-To: <CADvTj4qFBuK8QaRf_PJ34WsSVSVJNMLV8sq-QqUC2vte2OJrqQ@mail.gmail.com>
James, All,
On 2018-12-15 04:15 -0700, James Hilliard spake thusly:
> On Sat, Dec 15, 2018 at 4:04 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2018-12-15 03:56 -0700, James Hilliard spake thusly:
> > > Wouldn't it make
> > > sense to have mesa3d and mesa3d-headers share the same package version
> > > so that only one needs to be bumped?
> > That's unfortunately not possible, see the comment in mesa3d-headers...
> I think you could turn mesa3d-headers into a virtual/fake package
> similar to how I did it with my systemd-boot patch. Then you wouldn't
> have to refer to variables in mesa3d.
No, because that would make mesa3d more complex, for little benefit, see
the commit log of 8138a36018 (package/mesa3d-headers: new package), in
which there is an blurb about that.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2018-12-15 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 8:10 [Buildroot] [PATCH v2 1/1] package/mesa3d: bump to version 18.3.1 james.hilliard1 at gmail.com
2018-12-15 8:26 ` Bernd Kuhls
2018-12-15 10:39 ` Yann E. MORIN
2018-12-15 10:56 ` James Hilliard
2018-12-15 11:04 ` Yann E. MORIN
2018-12-15 11:15 ` James Hilliard
2018-12-15 13:40 ` Yann E. MORIN [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=20181215134023.GG2625@scaer \
--to=yann.morin.1998@free.fr \
--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