Dear all,

I did not take care until now of all my .pacnew files !
Hopfully, my system doesn't seems broken, and I am now merging all these
files.


I of course read the WIKI, and decided to use sdiff, as I do not feel
comfortable with VI for now.

Unfortunately, I found some very fancy results when using :
*sdiff -sa -o etcfilenew etcfile etcfile.pacnew*
(I use etcfilenew to check before I replace).
I don't know why, but this command didn't return many times the wanted
result: list all uncommon lines.


I know there are some scripts around, but I am not a big fan of using
scripts I do not understand.


So for now I deal with the classic diif.

Is there a simple command line I can use, appart sdiff and Vimdiff??

TY for your help.

On Sun, Jun 24, 2012 at 6:02 PM, Arno Gaboury <arnaud.gaboury@gmail.com> wrote:
> Is there a simple command line I can use, appart sdiff and Vimdiff??

if use pacdiff from pacman-contrib


--
Sébastien "Seblu" Luttringer
www.seblu.net

On Sun, Jun 24, 2012 at 06:28:15PM +0200, Sébastien Luttringer wrote:
> On Sun, Jun 24, 2012 at 6:02 PM, Arno Gaboury <arnaud.gaboury@gmail.com> wrote:
> > Is there a simple command line I can use, appart sdiff and Vimdiff??
>
> if use pacdiff from pacman-contrib

AFAIK pacdiff uses vimdiff too.

@ Arno

If you are not comfortable with vimdiff, you can try meld. It is graphical,
though.

On 06/25/2012 06:55 AM, gt wrote:

On Sun, Jun 24, 2012 at 06:28:15PM +0200, Sébastien Luttringer wrote:

On Sun, Jun 24, 2012 at 6:02 PM, Arno Gaboury <arnaud.gaboury@gmail.com> wrote:

Is there a simple command line I can use, appart sdiff and Vimdiff??

if use pacdiff from pacman-contrib

AFAIK pacdiff uses vimdiff too.

@ Arno

If you are not comfortable with vimdiff, you can try meld. It is graphical,
though.

I couldn't find any doc about pacdiff.
I manually merged all my pacnew files using oldschool diff and a text
editor. Not very conveniant, but it did the job.
Now playing finally with Vimdiff, as there is a lot of good doc. Even if
I am lost with all these keyboard commands, I like the dual screen
interface, and think I will stick to it. I will maybe add an entry in
the *Pacnew and Pacsave* *files*, as I think a list of most used
shortcuts could be explained.


TY for all your advices.

On Mon, Jun 25, 2012 at 7:00 AM, Arno Gaboury <arnaud.gaboury@gmail.com> wrote:
> On 06/25/2012 06:55 AM, gt wrote:
> I couldn't find any doc about pacdiff.
> I manually merged all my pacnew files using oldschool diff and a text
> editor. Not very conveniant, but it did the job.
> Now playing finally with Vimdiff, as there is a lot of good doc. Even if I
> am lost with all these keyboard commands, I like the dual screen interface,
> and think I will stick to it. I will maybe add an entry in the *Pacnew and
> Pacsave* *files*, as I think a list of most used shortcuts could be
> explained.
>
> TY for all your advices.

Dear Arno,

It's good that you find your way of dealing with pacnew files. Please
take a look at the wiki page
https://wiki.archlinux.org/index.php/Pacnew_and_Pacsave_Files
And the forum link posted at the end of the wiki.

Another helpful tool is pacmatic
(https://wiki.archlinux.org/index.php/Pacmatic#Consider_Using_Pacmatic)
It automatically informs you if pacman created any pacnew files that
you have to deal with.

A command like the:
locate -e --regex ".pac(new|orig|save)$"
will help you find any pacnew files you have on your system, I usually
use this in case I left over some when I did the merge and didn't
delete the file after.

Regards
Leonidas

--
Caution: breathing may be hazardous to your health.

#include <stdio.h>
int main(){printf("%s","x4cx65x6fx6ex69x64x61x73");}

On 06/25/2012 09:16 AM, Leonidas Spyropoulos wrote:

On Mon, Jun 25, 2012 at 7:00 AM, Arno Gaboury <arnaud.gaboury@gmail.com> wrote:

On 06/25/2012 06:55 AM, gt wrote:
I couldn't find any doc about pacdiff.
I manually merged all my pacnew files using oldschool diff and a text
editor. Not very conveniant, but it did the job.
Now playing finally with Vimdiff, as there is a lot of good doc. Even if I
am lost with all these keyboard commands, I like the dual screen interface,
and think I will stick to it. I will maybe add an entry in the *Pacnew and
Pacsave* *files*, as I think a list of most used shortcuts could be
explained.

TY for all your advices.

Dear Arno,

It's good that you find your way of dealing with pacnew files. Please
take a look at the wiki page
https://wiki.archlinux.org/index.php/Pacnew_and_Pacsave_Files
And the forum link posted at the end of the wiki.

Another helpful tool is pacmatic
(https://wiki.archlinux.org/index.php/Pacmatic#Consider_Using_Pacmatic)
It automatically informs you if pacman created any pacnew files that
you have to deal with.

A command like the:
locate -e --regex ".pac(new|orig|save)$"
will help you find any pacnew files you have on your system, I usually
use this in case I left over some when I did the merge and didn't
delete the file after.

Regards
Leonidas

Just installed pacmatic and did my first *$pacmatic -Syu*. Not bad
indeed. TY for the pointer.


I do think I am ready now to keep my pacman files updated with vimdiff.
There are not so many shortcuts to learn indeed, and finally found it
less scary for a beginner than vim

On 06/25/2012 02:42 PM, Kevin Chadwick wrote:

I like the dual screen
interface, and think I will stick to it. I will maybe add an entry in
the *Pacnew and Pacsave* *files*, as I think a list of most used
shortcuts could be explained.

Would be good if you copied that to this thread?

--
__________________________________________________ ______

Why not do something good every day and install BOINC.
__________________________________________________ ______
What do you want me to copy in this thread? All most common keyboard
commands using vimdiff?

The 24/06/12, Sébastien Luttringer wrote:

> if use pacdiff from pacman-contrib

There's an awesome package out there to do exactly this stuff at Gentoo:
dispatch-conf

http://en.gentoo-wiki.com/wiki/Dispatch-conf

It would be really nice if someone could hack on this tool to adapt it
to arch by forking it or by submitting patches upstream.

--
Nicolas Sebrecht

> I like the dual screen
> interface, and think I will stick to it. I will maybe add an entry in
> the *Pacnew and Pacsave* *files*, as I think a list of most used
> shortcuts could be explained.

Would be good if you copied that to this thread?

--
__________________________________________________ ______

Why not do something good every day and install BOINC.
__________________________________________________ ______

> If you are not comfortable with vimdiff, you can try meld. It is graphical,
> though.

Diffuse is pretty cool too and kdiff3 for folders. Just to be clear I
wouldn't give a gui program root for the final install though.

--
__________________________________________________ ______

Why not do something good every day and install BOINC.
__________________________________________________ ______