From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Gleb Mazovetskiy <glex.spb@gmail.com>
Cc: Samuel Martin <s.martin49@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 2/2] package: add smpq
Date: Wed, 20 Oct 2021 22:34:57 +0200 [thread overview]
Message-ID: <20211020223457.29d301e3@windsurf> (raw)
In-Reply-To: <CADjhFRBrddV3BCrC7FOEaBjzzvpWDshvO3SCA8Cq1uXby4at1Q@mail.gmail.com>
Hello Gleb,
On Sun, 17 Oct 2021 09:05:34 -0500
Gleb Mazovetskiy <glex.spb@gmail.com> wrote:
> The use case for me is to build DevilutionX (Diablo 1 source port) in a
> gaming-oriented buildroot-based distro (batocera.linux).
>
> DevilutionX produces an MPQ archive during the build process using smpq, so
> smpq needs to be a host package.
OK. But are you going to submit DevilutionX as a Buildroot package? My
only concern is that just by itself, smpg is not very useful. So having
that in Buildroot without having any of the packages that use it and
that provide some "useful" functionality is not very interesting from a
Buildroot maintenance point of view.
> I'm not near a computer for the next few days so I'd appreciate if you
> could adjust the commit message and DEVELOPERS when merging.
No worries about the timing, we're not in a hurry. There might be other
aspects in your patches to review, but I'd like first to understand
whether we want these packages in Buildroot in the first place.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-20 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 17:09 [Buildroot] [PATCH] package: add smpq and stormlib Gleb Mazovetskiy
2021-10-10 21:07 ` Yann E. MORIN
2021-10-11 21:00 ` [Buildroot] [PATCH v2 1/1] " Gleb Mazovetskiy
2021-10-11 21:02 ` [Buildroot] [PATCH v3 " Gleb Mazovetskiy
2021-10-11 21:21 ` [Buildroot] [PATCH v4 0/2] package: add smpq and StormLib Gleb Mazovetskiy
2021-10-11 21:21 ` [Buildroot] [PATCH v4 1/2] package: add stormlib Gleb Mazovetskiy
2021-10-11 21:21 ` [Buildroot] [PATCH v4 2/2] package: add smpq Gleb Mazovetskiy
2021-10-17 9:37 ` Thomas Petazzoni
2021-10-17 14:05 ` Gleb Mazovetskiy
2021-10-20 20:34 ` Thomas Petazzoni [this message]
2021-10-21 0:08 ` Gleb Mazovetskiy
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=20211020223457.29d301e3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=glex.spb@gmail.com \
--cc=s.martin49@gmail.com \
--cc=yann.morin.1998@free.fr \
/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