All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Knight <james.d.knight@live.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC PATCH] package/google-material-design-icons: drop package
Date: Wed, 9 Aug 2023 20:40:36 +0200	[thread overview]
Message-ID: <20230809204036.6da07ad8@windsurf> (raw)
In-Reply-To: <SN4P221MB068257366E0B70F2D1EC85B6A0689@SN4P221MB0682.NAMP221.PROD.OUTLOOK.COM>

On Sat, 29 Apr 2023 15:52:24 -0400
James Knight <james.d.knight@live.com> wrote:

> Newer versions of Google's Material Design icon package are structured
> differently, making a version bump no so trivial. While work can be done
> to support this, considering this package is using v2.2.3 and the most
> recent version is v4.0, it is most likely that this package is not being
> used. Environments which desire Material icons/fonts/etc. will most
> likely achieve better results be managing their own custom package to
> have an explicit selection/filter of design styles (e.g. standard,
> Android, etc.), variants (basic, outlined, rounds, etc.), display
> resolutions and scale selection desired.
> 
> Signed-off-by: James Knight <james.d.knight@live.com>
> ---
> This package (v2.2.3) was added sometime ago, to be a helpful for board
> builds that could easily install Material icons under `/usr/share` to
> be used by applications/web services (if configured for it). The
> original (external) project this was designed for was prototype-only,
> and is no longer used. I'm not sure that there is any value into
> maintaining this package in Buildroot since I suspect no other projects
> use it (mainly since it's two major releases behind and no one has
> requested a newer version).

Nobody complained, you originally contributed this package and no
longer willing to maintain it, so fair enough, patch applied to next. I
dropped the entry in DEVELOPERS and added the entry to Config.in.legacy.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-08-09 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 19:52 [Buildroot] [RFC PATCH] package/google-material-design-icons: drop package James Knight
2023-08-09 18:40 ` Thomas Petazzoni via buildroot [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=20230809204036.6da07ad8@windsurf \
    --to=buildroot@buildroot.org \
    --cc=james.d.knight@live.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.