From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add first KF5 packages
Date: Wed, 14 Feb 2018 21:29:43 +0100 [thread overview]
Message-ID: <20180214212943.3aa126a5@windsurf.lan> (raw)
In-Reply-To: <hrvclexdar.ln2@ID-313208.user.individual.net>
Hello,
On Wed, 14 Feb 2018 06:59:45 +0100, Bernd Kuhls wrote:
> according to the buildroot manual[1], section 17.1, new subdirectories,
> like package/kf5/, are discouraged, please add the new packages directly
> to package/.
I do agree in general. However, kf5 like qt5 is a group of packages
that share the same site/version number, and in that case, like we do
for qt5, a subdirectory is acceptable.
I'm also not a big fan of sub-directories, but it's the only sane way
to share version/site variables.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-14 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 21:35 [Buildroot] [PATCH 1/1] Add first KF5 packages Pierre Ducroquet
2018-02-13 21:53 ` Thomas Petazzoni
2018-02-13 22:02 ` Pierre
2018-02-14 5:59 ` Bernd Kuhls
2018-02-14 8:44 ` Pierre
2018-02-14 20:29 ` 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=20180214212943.3aa126a5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox