Package Details: mint-artwork 2:1.8.1-0

Git Clone URL: https://aur.archlinux.org/mint-artwork.git (read-only, click to copy)
Package Base: mint-artwork
Description: Linux Mint Artwork and Resources.
Upstream URL: http://packages.linuxmint.com/pool/main/m/mint-artwork
Keywords: cinnamon mint mint-artwork
Licenses: GPL
Groups: cinnamon
Conflicts: lightdm-gtk-greeter, lightdm-gtk-greeter-settings, mint-sounds
Submitter: OdinVex
Maintainer: OdinVex
Last Packager: OdinVex
Votes: 23
Popularity: 0.67
First Submitted: 2021-03-05 03:18 (UTC)
Last Updated: 2024-04-15 17:10 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

Cromer commented on 2022-02-15 14:59 (UTC)

Typically what is done is put an echo with the message in the install file.

Doing it via an echo is preferable because the user could be updating via tty or over ssh, and we can guarantee they see the message if done with an echo.

OdinVex commented on 2022-02-15 14:43 (UTC)

@Cromer, If I did decide to remove it to give the decision to the user, which way'd be best? notify-send?

OdinVex commented on 2022-02-14 20:48 (UTC)

@Cromer, Ah, right. Multitasking an insurance issue over phone, kinda breaks concentration.

Cromer commented on 2022-02-14 20:39 (UTC)

I said arch's repos, not the AUR.

OdinVex commented on 2022-02-14 20:02 (UTC) (edited on 2022-02-14 20:12 (UTC) by OdinVex)

@Cromer, Surprised you could grep the entire AUR on such a whim. It'll call it, until someone can come up with a solution to prevent losing entire DE settings/half-corrupt/inability to login/crash-looping (or someone can confirm none of those issues occur after installing without systemctl -- background: installing and then changing settings without logging out/in can cause some settings in Cinnamon to half-ass and break Cinnamon (crash-loop, lost/corrupt settings) -- at least in v1.4.* when initially created. Just to note, the first post does mention this package should be initially installed on a clean installation, just to be safe.). It wasn't an easy decision to make, including it.

Cromer commented on 2022-02-14 19:30 (UTC)

@OdinVex, no package should ever call systemctl from the install script. By restarting lightdm it logs the user out causing them to lose everything that they have open. Not a single package on all of arch's repos calls systemctl and yours shouldn't either.

OdinVex commented on 2022-02-13 19:24 (UTC) (edited on 2022-02-14 13:07 (UTC) by OdinVex)

@SunRed, It is necessary, systemctl is needed to restart the DM to prevent settings issues. As I mentioned earlier, if you want to be the one to test an upgrade without systemctl then feel free to reinstall while taking the line out and monkey with your settings and log out/in. Settings saved overwrite upgraded ones and can half-muck things. That was the test result with 1.4.*.

SunRed commented on 2022-02-13 19:00 (UTC)

@yochananmarqos: Ah, I see, thank you. I knew about pacman hooks but I didn't know there was one for gsettings schemas. In that case an install file shouldn't be necessary anymore at all.

OdinVex commented on 2022-02-13 18:18 (UTC) (edited on 2022-02-13 18:21 (UTC) by OdinVex)

@yochananmarqos, Ah, I see that. Updated.

yochananmarqos commented on 2022-02-13 17:50 (UTC) (edited on 2022-02-13 18:36 (UTC) by yochananmarqos)

@SunRed:

In your install file you should also create a hook for post_upgrade

No, he shouldn't. There's been a glib-compile-schemas hook since 2016, see package guidelines.

@OdinVex: Please revert the change.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »