New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Funny downstream bugs: we should have a category for these ones and never close them #1522
Comments
We can't make people read when they don't want to but yes, a FAQ will be useful (don't we have a FAQ)? |
krusader, lumina-fm... pcmanfm-qt isn't the only lightweight Qt file manager, man lol.
pcmanfm-qt:
I guess my point here is 1) your statements are not really correct in that bug posting (lumina-fm is lightweight and has no glib2 deps) and 2) for me, pcmanfm-qt has been a relatively buggy (to the point where I find it worth replacing) desktop manager and file manager. I just recentlly had to delete my entire config file for it so that I could change directories. |
@simoniz0r You really get the intention of the bug? If not - again: pcmanfm-qt is technically not a part of LXQt, was never and will never be - and that from the very beginning - beside of that it is our preferred choice for obvious reasons. And yes, one is free to chose whatever fit one needs. But that was not the point. The point of this bug is that pcmanfm-qt uses glib and to some degree other GTK libs - and this is not a bug. Second, we working on it to eliminate the not really wished dependencies. But i will not consider that having these dependencies in former versions as a bug - it was/is annoying, nothing more, nothing less. Thats all. And i can partly understand that Jonas was not amused - but thats life. |
Then why is it set as the default desktop manager on every LXQt install that I've ever done? |
because we think that we like it that way - thats all. And you are wrong here. I delivered my first LXQt release back in 2014 with pcmanfm as default. |
Oh, so I guess you must know that I've installed LXQt in 2014. Oh wait, that didn't happen. You shipping pcmanfm-qt as a default app in every current LXQt install (it happens in the places where you guys have full control over the packaging) tells me that it's an LXQt application. You depending on it for xdg-open to work properly, for being a desktop manager, etc tells anyone even more that it's part of LXQt from any normal user's perspective. |
i don't know how other distributions handle that - but the file manager is still interchangeble:
and the xdg-open assumtion is also clearly wrong:
But hey - maybe i don't understand some things. |
That's hardly valid as all of LXQt is replacable pretty much. Also, when did they fix xdg-open upstream? open_generic is still a not at all good solution (pcmanfm-qt was actually a better solution, but still not up to par with other DEs). |
oh - depending on their current working speed: somewhen |
Additonal - our preferred open implementation would be something like this: #1298 (comment) |
That simply means you don't understand quality at all -- which isn't a surprise to me. |
What are you even on about? pcmanfm-qt crashes much more frequently than lumina-fm for me. Also, being less offensive might do you well. |
As the author of pcmanfm-qt, here are my two cents:
You are free to choose whatever you like anyways. Free software is all about freedom. |
@tsujan - just reading your response to the debian bug - and all parties are right - it was my intention as the maintainer of the package to depend pcmanfm-qt on the libfm-modules for a reason: In the past years i heared complaints about pcmanfm and pcmanfm-qt not being able to handle things like smb etc. After the 10th or 20th of these complaints the decision was to depend on the modules - with all pro's and con's because our users don't install this or even better do a:
or more common
and complain afterwards about missed functionality and matureness of LXQt. So i put in all the things that are important as dependency just to prevent false claims. It wasn't funny anymore to hear such complains as in "LXQt isn't ready for debian/stable, because of lacking basic functionality etc pp" PS: And my life is better with just one not so happy user/developer than the other way around. |
@agaida Most users mistake GLib for GTK; I wanted to make it clear that we use GLib, not GTK. As far as I know, the git libfm-qt doesn't depend on libfm anymore but Arch's PKGBUILD still has that dependency. I don't know what's recommended with libfm-qt in Debian. In Arch, I see nothing and that's bad: At least, all gvfs packages should be recommended, IMO. Am I the only one that thinks libfm-qt doesn't depend on libfm anymore? Am I missing something? |
yes, you missed something important - distributions have our latest release in their repositories (ok, i correct myself: should have 🕶️ ). And this is mostly not about the libfm-qt, it is about pcmanfm-qt. Some of the big rewrites was introduced after our last release and are the cause for bumping the soname ... |
OK. BTW, it's still soon for the next release, mainly because of SMB problems and partly because we should test the recent changes more. |
right |
Expected Behavior
Downstream Developers should read and understand the code or documentation before writing a bug.
Current Behavior
Some don't.
Possible Solution
Maybe introduce a short Q & A page in the wiki with questions like:
Steps to Reproduce (for bugs)
Read some bug trackers, like that: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903836
Context
Handling downstream wrong claims.
The text was updated successfully, but these errors were encountered: