Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A accountsservice
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 64
    • Issues 64
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • accountsservice
  • accountsservice
  • Issues
  • #2
Closed
Open
Created Nov 08, 2013 by Bugzilla Migration User@bugzilla-migration

Overrides for vendor extensions

Submitted by Iain Lane

Assigned to Iain Lane

Link to original bug (#71393)

Description

Similar in spirit to GSettings overrides, it'd be nice if the new vendor extensions could be overridden too. For things like OEMs customising distribution defaults or distros changing upstream defaults.

Working on a patch to implement this. I'll probably copy the GSettings approach: arbitrary named .override files alongside the extension they are overriding, with the latest one winning. File format will be key files.

,---- | [interface] | property=newdefault `----

Yell if you think this should be different.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking