[neon] [Bug 406712] applications associated with cantor backends should not be strong dependencies but recommendations

2019-04-28 Thread avlas
https://bugs.kde.org/show_bug.cgi?id=406712 avlas changed: What|Removed |Added Resolution|NOT A BUG |INTENTIONAL --- Comment #5 from avlas --- Another

[neon] [Bug 406712] applications associated with cantor backends should not be strong dependencies but recommendations

2019-04-24 Thread avlas
https://bugs.kde.org/show_bug.cgi?id=406712 --- Comment #4 from avlas --- (In reply to Harald Sitter from comment #1) > That would also allow "breaking" cantor, which as far as the deb dependency > line-up is concerned is not something that should be allowed. Mixing the > stack like this simply

[neon] [Bug 406712] applications associated with cantor backends should not be strong dependencies but recommendations

2019-04-23 Thread avlas
https://bugs.kde.org/show_bug.cgi?id=406712 --- Comment #3 from avlas --- In fact, Cantor backends are plugins/addons. There are many applications out there that do the same without breaking the application. For instance, Okular has recently introduced support for TexStudio as editor and this

[neon] [Bug 406712] applications associated with cantor backends should not be strong dependencies but recommendations

2019-04-23 Thread avlas
https://bugs.kde.org/show_bug.cgi?id=406712 --- Comment #2 from avlas --- (In reply to Harald Sitter from comment #1) > That would also allow "breaking" cantor, which as far as the deb dependency > line-up is concerned is not something that should be allowed. I respect what you say but I would

[neon] [Bug 406712] applications associated with cantor backends should not be strong dependencies but recommendations

2019-04-23 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=406712 Harald Sitter changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED