Skip to content

BlankOn branding into the base-files package#3

Open
Adekabang wants to merge 3 commits intoblankon-packages:masterfrom
Adekabang:master
Open

BlankOn branding into the base-files package#3
Adekabang wants to merge 3 commits intoblankon-packages:masterfrom
Adekabang:master

Conversation

@Adekabang
Copy link

This pull request introduces BlankOn branding into the base-files package by adding new logo assets, registering them as vendor logos, and updating installation scripts and metadata. The changes ensure that BlankOn logos are installed in the appropriate directories, set up as the system's default vendor logos with higher priority than Debian's, and referenced in the system's release information.

Branding and Asset Installation:

  • Added installation steps for BlankOn logos in multiple locations, including /usr/share/pixmaps, /usr/share/icons/hicolor/scalable/apps, and created a structured /usr/share/blankon-logos directory for use as vendor logos. (debian/rules, debian/base-files.dirs) [1] [2]
  • Registered BlankOn logos as the default vendor-logos alternative with priority 100, overriding Debian's default, and set up symbolic links for various icon sizes and formats. (debian/postinst)

System Integration:

  • Added LOGO=blankon-logo to etc/os-release so system components can reference the new logo.
  • Updated the changelog to document the addition of BlankOn logos, their installation, and the vendor-logos alternative registration. (debian/changelog)

Compatibility and Packaging:

  • Declared replacement of gnome-control-center-data to avoid file conflicts with existing logo assets. (debian/control)

- Add BlankOn logo files (PNG and SVG variants)
- Create /usr/share/blankon-logos directory structure
- Register as vendor-logos alternative with priority 100
- Install logos to /usr/share/pixmaps and hicolor icons
- Add LOGO=blankon-logo to os-release
- Add gnome-control-center-data to Replaces field

This replaces Debian logo in GNOME Settings > About with BlankOn logo.
Copy link

@luckynee luckynee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me, @herpiko is it okay to have 2 maintainer for the same package?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants