-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Status of packaging the Deepin Desktop Environment (DDE) #94870
Comments
This was also on my mind as well, it seems that having the desktop environment won't be feasible for us atm without a contact point inside Deepin. I believe other distro's that were packaging Deepin have had to make similar calls. One notably was OpenSUSE, which was instigated by some serious security issues in regards to dbus. And things like that could only be handled better with a security contact. IMHO, this project would be okay to abandon and remove the desktop packages from nixpkgs. However, I believe some of the applications could remain in nixpkgs, or is there an issue with even those? You are in no way inclined to maintain those if you do not wish too, but I'd think at the bear minimum those shouldn't be too difficult to keep in nixpkgs. Let me know what your thoughts are, and re your ping on IRC (which I assume might be in relation to this), if you need to discuss further we should do so in a PM either on Freenode or if you're available on Matrix. If we do decide to remove all or a large portion of DDE we should try to do it in a clearly defined way. Making sure we have release notes and the not cosmetically elegant |
Hmm, I didn't read closely this point
Yeah, I think I have an idea as to what the issue there is, but it sounds like it would be better to just remove them entirely. |
I have a local branch where I am trying to follow recent releases of the packages. Some of the issues I am seeing with the applications are referred to here. Also here. Upstream have migrated applications from GTK to DTK (the Deepin Desktop Toolkit), which is based on Qt. I have forgot to mention also that most of the discussions available on upstream github repositories are in Chinese, which I can not read. |
@romildo Could we remove this before 20.09 release? (so it's not in 20.09) |
I just want to say one thing, I've only ever used a single deepin software (screenshot) and it's absolutely the best screenshot software I've ever used including on windows. There is no point in removing what already works until it starts breaking or it deals with files downloaded from internet. Deepin screenshot is, to me, an example of how user friendly software is written. |
@asdf8dfafjk I would agree, deepin-screenshot was even better than flameshot which is very similar. I use elementary-screenshot which has a very good flow, it's just lacking all the features the latter have. I guess we can also close this issue since the status of packaging DDE is that it is now abandoned. |
While my comment was specifically about deepin, I would say it would be great if you leaders could have a policy of sorts on removing a package. Personally I would wait until its broken or there is a security risk in some adversarial model. (screenshot, for example, doesn't have one in my limited understanding). |
@asdf8dfafjk I think collectively maintainers of desktop managers should be responsible for deciding if we should have a different DE added into nixpkgs and what expectations are going to be made of it. And yes, having policies for these things is actually a thing I've discussed in length in some videos (I think?) and on discourse. I believe the deprecation RFC would be something you're interested in, since it essentially covers this. |
@asdf8dfafjk You can argue that for packages that are abandoned upstream but for live software there is another issue – including a package that is out of date has a negative impact not just on us as a distribution but at the upstream project as well, see for example the Debian vs xscreensaver drama. We cannot be good free software citizens while essentially misrepresenting the upstream project by shipping an outdated version. |
@worldofpeace My point was about individual softwares where the quality is so high that its clear that an archived software still beats others. That said, since you say there already exists and policy and since you and romildo seem to be the maintainers, I defer. |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/progress-on-portingthe-deepin-desktop-environment-dde-to-nixos/20733/1 |
nixos/doc/manual/release-notes/rl-2009.section.md said netease-cloud-music depends on deepin desktop environment and because deepin desktop environment had been removed, netease-cloud-music is also removed. However, it seems that netease-cloud-music can work without deepin desktop environment. So I package it again. NixOS#94870 removed DDE NixOS-CN/flakes#51 recommend to push this package to NixOS/nixpkgs
Some time ago I have started an effort to package the Deepin Desktop Environment for NixOS, with the help of @worldofpeace. It has been a difficult task. In the following I comment some aspects of it.
It has taken too much of my time to try to evolve DDE on NixOS. As I have no expertise on Qt development, the issue of making KWin work for DDE seems too difficult also.
Considering all of this, I am inclined to abandon this project and remove the packages from nixpkgs.
I would like to know what other NixOS developers think about this situation. What directions should we follow?
cc @worldofpeace @jtojnar @ttuegel
The text was updated successfully, but these errors were encountered: