Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] [RFC] unvendor desktop files, icons, and similar files from the srcpkgs tree
@ 2024-03-07  3:19 classabbyamp
  0 siblings, 0 replies; only message in thread
From: classabbyamp @ 2024-03-07  3:19 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

New issue by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/49164

Description:
there are a number of packages that include void-created `.desktop` files, icons, and sometimes even other things like manual pages in `srcpkgs/<pkg>/files/`, when files like this should come from upstream or not at all. In a quick survey I did in the past, some of the vendored desktop files even have upstream-provided ones available! (in those cases, the desktop files we have are often outdated or different from upstream)

A rough count finds:
- 91 `.desktop` files (a few should stay, like pipewire's)
- 43 PNG, 2 xpm, and 2 SVG icons

IMO, most, if not all, of these should be removed and either replaced with an existing upstream one or contributed upstream. I'd be interested in working on that if it is desired.

It would also be nice to add some kind of lint for the future to prevent these from slipping in again, as I see it often in new package PRs.

@void-linux/pkg-committers thoughts?

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-03-07  3:19 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-07  3:19 [ISSUE] [RFC] unvendor desktop files, icons, and similar files from the srcpkgs tree classabbyamp

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).