debiancn / galternatives Goto Github PK

View Code? Open in Web Editor NEW

5.0 6.0 3.0 764 KB

Configuration tool for Debian alternatives system (mirror, will be overwritten!)

Home Page: https://salsa.debian.org/chinese-team/galternatives

License: Other

Python 97.50% Makefile 2.50%

debian python3 system-management gtk3

galternatives's Introduction

Note: GitHub mirror is also available for forking/PR/translating.

G Alternatives is a tool that provides a simple GUI interface for update-alternatives, allowing system administrator to select which programs provide specific services for the user by default. Some advanced features are also provided, including adding/removing/editing alternative groups/options or managing a custom database directory.

Python 3 required. It's intended to be installed via apt install galternatives, but for those who don't like to install, the tarball (python3 -m galternatives) should also work.

Any question or enhancement is welcomed. Please send your feedback to package maintainers of galternatives package in Debian or submit bugs onto Debian Bug Tracking System (BTS) using reportbug tool in Debian.

Requirements

Gtk+ >= 3.10
python3
python3-gi
gettext (for i18n support)

Packaging repository

Official packaging and development repository: Salsa chinese-team/galternatives

License

GPL-1+ for the whole project. See LICENSE.GPL-1, LICENSE.GPL-2 and LICENSE.GPL-3 for full license text. GPL-2 is chosen as the representative (LICENSE file).

galternatives's People

Stargazers

Watchers

Forkers

scootergrisen egomi24 p-bo

galternatives's Issues

Add comment for translator_credits

Perhaps add comment to:
msgid "translator_credits"

So translators know what to write and not actually translate the string.
Seems its be translated wrongly in french at least:
https://github.com/debiancn/galternatives/blob/master/resources/translations/fr.po#L157

Migration to Python3

We need to migrate all python scripts to python3 syntax.

Description on alternative name

Currently the latest stable version provides a strange way to supply a short description on the alternative name by using an almost-vaild .desktop file. However after some searches I can't find any more of such files nor descriptions. So I'd suggest:

provide more descriptions using the old way
provide more descriptions directly using gettext
remove the description feature at all (since it's quite a huge task)
Which one do you perfer?

Splitting frontend/backend code in python scripts

We wish to split current code into two parts:

A python3-galternatives library, which only deal with manipulation of Debian alternatives system;
Some frontend code as an application.

Licens says both GPL-1+ and v2.0

On https://github.com/debiancn/galternatives#license it says GPL-1+ but https://github.com/debiancn/galternatives/blob/master/LICENSE it says v2.0.

Move project from glade-2 to glade-3

Current glade (glade 3.x) does not recognize glade2 project file in the project.

We need to convert the project soon.

Research on permissions and integration with polkit

Currently galternatives does not need root password to gain root permission. We need to learn how it works and see what we can do.

Review i18n/l10n workflow

We need to sort out the i18n/l10n workflow.

.glade files contains some strings that need translation. (perhaps we need xgettext?)
.py module needs translation.

We should write some scripts / Makefile targets / update current scripts to make sure things go on smoothly.

zh_CN.po and zh_TW.po have problem with {2} {4}

zh_CN.po and zh_TW.po have a problem with these translations where it says 3 and 2 in the source but 2 and 4 in the translations (4 does not exists in the source string).

Maybe someone who knows chinese can fix it.

zh_CN.po:

#: ../../galternatives/description.py:140
#, python-brace-format
msgid "Install option `{3}' for group `{2}'"
msgstr "为组`{2}'安装选项 {4}"

zh_TW.po:

#: ../../galternatives/description.py:140
#, python-brace-format
msgid "Install option `{3}' for group `{2}'"
msgstr "為組`{2}'安裝選項 {4}"

PEP8 coding style

Should we follow the PEP8 convention?

Package style modernization

Review packaging scripts in debian/ directory and do necessary modernization jobs.