#trinity-desktop < 2021/07/28 > |
| [01:33] | FireSnake_ has quit (Remote host closed the connection) |
| [01:39] | FireSnake_ has joined |
| [02:13] | micheleC has joined |
| [03:20] | micheleC has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org) |
| [03:33] | FireSnake_ has quit (Remote host closed the connection) |
| [03:38] | FireSnake_ has joined |
| [04:22] | FireSnake_ has quit (Remote host closed the connection) |
| [04:28] | FireSnake_ has joined |
| [05:11] | selk has quit |
| [08:58] | pitriss: Hi guys. Just an idea.. How about splitting amarok's backends into separate files.. Why the heck user needs to have installed metric f**kton of packages that he is not planning to use.. Eg I used sqlite, why do I need libmysql and so on? That makes this software way less usable. Imo when there will be amarok-backend-mysql, amarok-backend-sqlite and amarok-backend-pgsql (maybe even with optional amarok-backends metapackage) it would make it less |
| [08:58] | pitriss: painfull to use |
| [09:46] | SlavekB-axis has joined |
| [10:40] | SlavekB-axis: Pitriss, yes, it is a good idea. We will probably have to edit the configuration wizard and setup window to offer only dbengines that are currently installed. |
| [10:41] | SlavekB-axis: Please, you can enter it as issue in TGW? |
| [10:47] | pitriss: SlavekB-axis: sure.. I wasn't sure if its doable/sane idea |
| [10:59] | pitriss: TDE/amarok#26 |
| [10:59] | tde-bot: [TGW][amarok] #26 - Detach backend libraries into separate packages |
| [10:59] | tde-bot: https://mirror.git.trinitydesktop.org/gitea/TDE/amarok/issues/26 |
| [14:19] | hunter has joined |
| [14:21] | hunter has quit (Remote host closed the connection) |
| [17:25] | SlavekB-axis has quit (Quit: TDE Kopete : https://trinitydesktop.org) |
#trinity-desktop < 2021/07/28 > |
© 2010-2025 Trinity Desktop Project