Simple EndeavourOS Maintenance “Cheat Sheet”

I mean like ..

Theres no mention of pacnew anywhere in this thread until that comment.

Maybe it was meant for a different thread?

Or you are saying a note about them should be added to this Cheat Sheat?

@cscs, just a guess, but I think he may have clicked the link in my OP where I give @fbodymechanic credit for his original A Complete Idiot’s Guide To Endeavour OS Maintenance / Update / Upgrade. He has a section in his original maintenance in which pacnew / pacdiff are utilized.

2 Likes

Oh yes… I did read the guide and it had stuff about the pacnew config files, OP caught my drift

2 Likes

Me too. Which is why I just want to make sure to mention most of what I wrote is directly from Arch. I’m not some Arch master, and don’t deserve too much credit.

2 Likes

@fbodymechanic, still… you created that initial thread. Simplified it so others could get a grasp relatively quickly.

And for that…

Thanks

3 Likes

For a while, we were getting “how to update” type threads here constantly. Especially as we went from year 0 to 2 and gained a lot of traction and popularity. I was trying to make a very simple thing we could just dump into every thread and not turn it into the same repetative thread where people keep getting lost in. I just wanted one (there’s more than one way to do a lot of this) simple starting point anyone could use. And make the lives of us regular users easier mostly.

I was actually trying to make our lives easier, not necessarily the new users LOL

5 Likes

glad you did. for all of us who use your Guide, or abridge it, I can say to anyone reading from around the world that my machine is better for it. Performance better too. The simple maintenance you compiled makes the Endeavour experience better, there is no doubt.

Would you mind please changing the suggested

To

DIFFPROG=meld pacdiff -s

This way the user can actually make/save changes when viewing the diffs.
(The s flag means it will use sudo, or actually sudoedit to work on temporary files and then apply changes afterwards using sudo.)
Without it the ‘view’ option really is just a view, and other functions like ‘remove’ wont work.
This may also have the result of users attempting to somehow ‘sudo pacdiff’ which wont be the correct approach.

1 Like

Maybe. I dunno. Maybe Joe or one of mods can fix or add if they want. The thread kept turning into an argument/disaster destined to be ruined by one of our famous moderators, so I gave up on it a while back. I think I’m going to stick to that giving up bit. It’s been ok for years. That’s good enough for me.

1 Like

I guess thats fine..

I woulda changed it myself if I could.

Its probably originated either from long enough ago that the s option did not exist, or from a source that did not realize it existed.

As it stands now the provided example will not actually allow management of the pacnew files through pacdiff. They will still have to manually apply changes themselves using some other method.

I understand also the consternation. In fact I’ve been chastised multiple times for trying to teach the proper way of managing pacnews. Over on Manjaro of course some didnt enjoy correction .. and Phil even proclaimed to have not ever managed a pacnew in their entire life - indeed not even knowing about them until a few years ago (having learned during one of those unappreciated corrections).

1 Like

I don’t remember. Actually, I owe that one to @Stagger_Lee as I believe he’s the one who gave me that. I don’t even know if the -s option existed then. I still didn’t realize it was a thing until just now when you told me. I’m a little too far out of the Arch thing these days. I feel like a retired backup athlete. I was barely enough to hang with anyone then, and now a days I’m just pudgy washup talking about glory days and don’t remember how I even got here.

Dont be so hard on yourself!

But also that was a pretty funny way to put things. :slight_smile:

Despair can be funny if you look at it correctly :rofl:

I feel like they’ve made a movie about it a time a or two.

Although, I’m realizing we’re doing exactly the thing that got me mad in my guide. If we want to ramble take it to PM/Telegram

1 Like

It’s been edited to reflect this change. :wink:

There we go. You finally got to make a productive contribution to the thread! Onward to 100k views!

1 Like

Jeez, overthinking is doing my nut in! :zany_face:

1 Like

Recommending the proper syntax so that one can actually use their set DIFFPROG to merge changes while using pacdiff is not overthinking.

But I digress.. we werent supposed to be be making unrelated comments here anymore. :speak_no_evil_monkey:

2 Likes

It was written a couple of months prior to the -s option being added to pacdiff:

Here’s the commit, from May 03 2022:

https://github.com/archlinux/pacman-contrib/commit/0a5c2e3c7c0ace9537300962fa22009af14fe270#diff-d975bf659606195d2165918f93e1cf680ef68ea3c9cab994f033705fea8238b2R11-R16

See the newly added line #11:

+ pacdiff: Add option to use sudo/sudoedit to manage files (19ab4fac)

1 Like