boxit issueshttps://gitlab.manjaro.org/tools/maintenance-tools/boxit/-/issues2018-06-09T13:35:07Zhttps://gitlab.manjaro.org/tools/maintenance-tools/boxit/-/issues/12update our user management2018-06-09T13:35:07ZPhilip Müllerupdate our user management*Created by: philmmanjaro*
With the current given user management every developer can
* sync from our upstream project Archlinux into any branch
* push/remove packages on any branch
* snap any branch to another
We may think abo...*Created by: philmmanjaro*
With the current given user management every developer can
* sync from our upstream project Archlinux into any branch
* push/remove packages on any branch
* snap any branch to another
We may think about
* restricting the whole possibilities to several sub-rights
* add new rights if neededhttps://gitlab.manjaro.org/tools/maintenance-tools/boxit/-/issues/11add blacklist option for overlay pkgs2018-06-09T13:35:07ZPhilip Mülleradd blacklist option for overlay pkgs*Created by: philmmanjaro*
Having a **excludelist** option for the **sync-folder** not to get certain packages from our upstream project **Archlinux** we may need to add also a **blacklist** option for our overlay packages, to hold some...*Created by: philmmanjaro*
Having a **excludelist** option for the **sync-folder** not to get certain packages from our upstream project **Archlinux** we may need to add also a **blacklist** option for our overlay packages, to hold some back within our **snap** function. This would give us the option to test or release packages to a certain branch but only hold it there.
As a workaround the **xperimental** branch got introduced to experiment with new packages without changing the current workflow of our distro.