| OvenWerks | Eickmeyer[m]: it sounds like a good sw updater is more difficult than thought? | 13:37 |
|---|---|---|
| Eickmeyer[m] | OvenWerks: Yeah. This is going to require some collaboration, which is OK. we can't do this on our own. | 14:21 |
| Eickmeyer[m] | Ubuntu Flavors aren't an island. We should always be collaborating with each other. The idea of being separate from the rest of Ubuntu isn't a thing. Tribalism gets us nowhere. The more we work together, the better things are for everyone. | 14:25 |
| Eickmeyer[m] | What I thought was funny was it attracted the attention from KDE (Neon) and Fedora. | 14:25 |
| OvenWerks | :) | 14:27 |
| Eickmeyer[m] | OvenWerks: FYI, the update-manager autoremove tells you exactly what it's removing and gives you the option to unselect stuff to keep it from removing it. | 17:10 |
| OvenWerks | Thats good. Is there also a way to flag packages set to auto remove as user installed? | 17:48 |
| OvenWerks | otherwise they remain in the autoremove list | 17:49 |
| Eickmeyer[m] | OvenWerks: Only way I know of to do that is "apt-mark manual {package}". | 18:45 |
| OvenWerks | exactly | 18:51 |
| OvenWerks | a GUI that shows a list of autoremove packages should have two check marks, one for yes remove and a second for keep this package. One could even argue, though I am not sure they would be right, that anything that remains un checked for removal, should be marked manual | 18:53 |
| OvenWerks | The main reason for not marking unchecked packages as manual, is that there is no "I don't want to make this decision right now button" :) | 18:54 |
| Eickmeyer[m] | That sounds like a feature enhancement request, which is a form of bug report. | 19:03 |
| Eickmeyer[m] | That said, it would come up on the next time upgrade-manager runs. | 19:03 |
| === arraybolt3_ is now known as arraybolt3 | ||
| === arraybolt3_ is now known as arraybolt3 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!