From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: void-artwork: update to 20220303.
Date: Tue, 15 Mar 2022 16:29:56 +0100 [thread overview]
Message-ID: <20220315152956.2ZfdTv_3xsN2lqpkkxeoB8aBTkfDV_4OQnc99WsXp0M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35942@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
There's a merged pull request on the void-packages repository
void-artwork: update to 20220303.
https://github.com/void-linux/void-packages/pull/35942
Description:
Adds an svg version of the logo, a script to generate icons from it, and generated icon files for the logo (with and without the VOID text) at various sizes, which are installed to the hicolor (fallback) icon theme.
The logo files are pre-generated to avoid makedep on librsvg-utils, and they are small enough and change so rarely that it is not a big deal to include them in git.
The source svg is slightly different than the one on alpha.de; it has a small white border added to help with legibility on dark backgrounds.
This is a follow-up to #35604
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
The logo shown at various sizes in `plasma-sdk`'s cuttlefish:
The logo shown in KDE settings using the new `/etc/os-release` from #35604:
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-03-15 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 7:27 [PR PATCH] void-artwork: update to 20220301 classabbyamp
2022-03-03 7:54 ` [PR PATCH] [Updated] " classabbyamp
2022-03-03 8:00 ` classabbyamp
2022-03-03 8:03 ` classabbyamp
2022-03-03 8:05 ` classabbyamp
2022-03-03 8:13 ` [PR PATCH] [Updated] void-artwork: update to 20220303 classabbyamp
2022-03-03 8:21 ` classabbyamp
2022-03-05 23:03 ` classabbyamp
2022-03-06 3:13 ` classabbyamp
2022-03-12 23:16 ` 0x5c
2022-03-12 23:20 ` 0x5c
2022-03-15 15:29 ` leahneukirchen [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=20220315152956.2ZfdTv_3xsN2lqpkkxeoB8aBTkfDV_4OQnc99WsXp0M@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).