[ralphy]

OK Jerry,

I have committed this feature request to master. In the process we cleaned up lite-tweaks-super zenity output and we also corrected a bug. 

[valtam]

[member=2]Jerry[/member] , what would it be a good place to store additional commands and files for Lite Tweaks? For example; I have done something about dry apt:

We execute dry apt as soon as Lite Tweaks is launched but we execute it in the background and as a separate process so that it does't interrupt Lite Tweaks execution:

Assumed location:

Code:

bash -c "/usr/share/litemodules/dryapt" &

Then dryapt contains the dry apt check that will be stored in a $USER location where it can be written to and read from:

Code:

#!/bin/bash
dryapt=$(apt-get -s autoremove | grep -Po '^Remv \K[^ ]+' | awk '{print $0}' | wc -w)
eval "${dryapt}" &>/dev/null &disown
echo "${dryapt}" > "$HOME/.local/share/.dryapt"

Finally, we can read the file $HOME/.local/share/.dryapt and if the content is 0 (zero) we do not show Autoremove Packages tweak else we show it. That's a way around to run this check in Lite Tweak without affecting its initial execution. Your opinion?

We could use /usr/share/local/sbin/ for storing additional commands. I see that the commit has already been made. I know I don't always respond in a timely manner, try to keep in mind that's because of work and real life demands. There is no hurry to get these things out, unless they are urgent security or bug issues that affect everyone. Nice job on this :)

[valtam]

Will test in the coming days.

[ralphy]

We could use /usr/share/local/sbin/ for storing additional commands. I see that the commit has already been made. I know I don't always respond in a timely manner, try to keep in mind that's because of work and real life demands. There is no hurry to get these things out, unless they are urgent security or bug issues that affect everyone. Nice job on this :)

I did it for reasons other than you not responding. I never worry when you don't respond timely; we have a life of our own and believe you me, I know exactly how that goes :)

I figured it would be useful to have a common place for additional scripts within our own LL paths and since I was working on it I did my own justice and figured /usr/share/litemodules would've been a good place so that we could chmod 755 everything under it (these files need the execute bit)... worst case scenario, we can always change the path and the code if you believe it to be necessary.  :)

[valtam]

I'm just mindful of keeping our files in fewer places rather than more. Using an existing folder just makes sense.

Sent from my Mobile phone using Tapatalk

[ralphy]

I'm just mindful of keeping our files in fewer places rather than more. Using an existing folder just makes sense.

I think you're right; /usr/local/sbin/ would have been a better folder after all since we already have updatesnotify script files there. I've taken note to move it and update the code and use /usr/local/sbin/ instead.

Agreed?
 

[valtam]

Yes please Ralphy, thank you.

Sent from my Mobile phone using Tapatalk

[ralphy]

dryapt file has been moved and updated accordingly. Changes committed to master.

p.s. We have upgraded many things in litesoftware and lite-tweaks. Please, if it is not too much to ask, do test and release updates for them. I have quite a lot of things to go over and I would like to update my DEV systems to the latest so that I can be up-par with what users are running.

I didn't find bugs in either script at this point but fresher eyes before releasing updates is always a good thing :)

I'm off now.

Cheers!

[valtam]

Will do. Cheers.

Sent from my Mobile phone using Tapatalk

[ralphy]

I think I found a bug... running some more tests now...

It was not really a bug but me overwriting my own work!  >:(  I have pushed the latest to master.