EbonJaeger Since Nemo is the repo now ( thanks for the change of heart on that respect ) .. whats the update path for current installs?
I saw in https://dev.getsol.us/R4536:49918d1770b80665467867888d639f03fc28cd16 a few things changed from the default config and i assume we have to do those changes ourselfs.
Other then that .. just install Nemo, uninstall Nautilus and done ?
TerohsLab As long as budgie-deskop-branding-fortitude-plus is installed, you'll have those detaults set automatically.
If you're only using Nemo as a file manager, then yeah, it's unpin Nautilus from the taskbar, pin Nemo, and optionally uninstall Nautilus.
If you want to use Nemo for desktop icons, I posted a guide here.
EbonJaeger I'm switching to Nemo once the sync lands, because "Drag and Drop" not working from zipped files is just .. beyond infuriating.
But i dont have Nemo installed yet.
Assuming once sync happens, Nemo gets auto installed and i just remove Nautilus.
Thank you !
TerohsLab Nemo will not get autoinstalled by updating. There isn't a way for us to do that without making it a dependency of something, meaning you couldn't uninstall it later if you wanted.
I plan to switch to Solus when the new 4.4 ISO officially releases in Q1 2023.
RAinb0wStAr9938 I plan to switch to Solus when the new 4.4 ISO officially releases in Q1 2023.
If you are planning to use Budgie, it makes sense to install clean from the 4.4 ISO rather than install 4.3 and switch file managers.
tomscharbach agree completely. I am waiting for that new iso to switch back. seems like 'best practices' with a new integrated file manager anyway then the mid-stream switcheroo.
I mean... If you're only using the file manager and not desktop icons all you have to do is install Nemo lol. There's nothing special about it.
Since I have been on the same Solus Budgie install since April 2019 I will probably stay on Nautilus. I hardly use the file manager anyway. More console work and Worker.
EbonJaeger I mean... If you're only using the file manager and not desktop icons all you have to do is install Nemo lol. There's nothing special about it.
Six of one, half dozen of the other, for existing Budgie users. But neither @RAinb0wStAr9938 nor @brent have Budgie currently installed, and there is an advantage of doing a clean install rather than cleaning up an old installation by installing and uninstalling. I would do a clean installation if I were in that situation, but then I think that it is a good idea to do a clean installation every year or two just to get the cruft out.
tomscharbach . I would do a clean installation if I were in that situation, but then I think that it is a good idea to do a clean installation every year or two just to get the cruft out.
concur with this again. new budgie, with Nemo, as baked into the flagship seems preferrable to me on a certain level because if I just did the switcheroo...and uninstalled nautilus...I would have to go hunt down all its files, folders, and directories, some with sudo permissions, some without, for purging, plus all the pyschic debris if you believe in that stuff. That said I know @EbonJaeger is right and nothing would change per se. I will await the day I can install the iso cleanly. Can dig it.
brent I would have to go hunt down all its files
There's a reason why eopkg has the rmo command. How many folders and directories do you think Nautilus requires?
That said, I agree that a fresh installation would be better. But you could do the other until the 4.4 .ISO files are available, and then do your fresh installation. Only if you want to, of course.
WetGeek There's a reason why eopkg has the rmo command. How many folders and directories do you think Nautilus requires?
As far as I know, rmo removes dependencies that are no longed associated with any installed package.
brent rmo and dc gets rid of some stuff. But eopkg in no way gets rid of an app's folders in .config, .local, etc etc. Eopkg doesn't remove a paper trail.
There won't be conflict with Nemo and leftover Nautilus files, though.
brent rmo and dc gets rid of some stuff. But eopkg in no way gets rid of an app's folders in .config, .local, etc etc.
That's right. Eopkg won't touch anything in your home directory.
I'm not sure where the "etc etc" folders are, but for the stuff in your home directory, it takes only a few seconds to turn on "show hidden files," then find the folders named "Nautilus" and rm -r them at their top level.
But as @[deleted] pointed out, with Nautilus removed, nothing will be looking for them so they're as good as removed even if you don't bother to do that. And it's only for (we're hoping) a short time until 4.4 .ISO files are released.
WetGeek I'm not sure where the "etc etc" folders are
those are likely more ./ folders plus whatever slithers into the / directory after install.
WetGeek But as @stalebrim pointed out, with Nautilus removed, nothing will be looking for them so they're as good as removed even if you don't bother to do that.
I am not a neat freak, but ^ that's not my style of housecleaning.
