[Bug 214987] New: extra or missing files when comparing two directories

[jay]

https://bugs.kde.org/show_bug.cgi?id=214987

           Summary: extra or missing files when comparing two directories
           Product: kompare
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kompare-devel at kde.org
        ReportedBy: plainj at ieee.org


Version:           3.5.4 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-15-generic

      This concerns the way kompare treats extra or missing files when
comparing
two directories.  The way I am trying to use it is to compare present website
contents with an earlier version of the website.
      Consider an extra file (which occurs when one edits and old file "foo"
and
does not erase the foo~ file that an application such as emacs creates.  
Kompare finds and reports the differences in the old and new foo correctly, 
but then  goes on to report that all of lines in the new foo~ file are
different 
than the "lines" in the non-existent "foo~" file in the old directory.  
    It would be more helpful if it were reported (in addition to the old and
new
foo file differences) that there was an extra file in the new version of the
directory named "foo~" and of course where it is located.
     There is a more serious consequence of the present kompare in the 
following case(s).
     Consider the addition of an new symbolic link in the new version of
the directory  (a symbolic link to a file outside the present directories 
being compared).  Ie. in directory old there is no
symbolic link, but in the new there is.   (Eventually when the directory is
burned to a CD,  or moved to the location of the active website, the linked 
file will get included, but prior to that there is just a new "symbolic link"
file.   Presently kompare reports that it cannot parse the new file.   But as
this 
is a new "file" it needs only be reported that way.  Ie. it's contents are not
of interest.
     If this is a departure from the way most code developers use kompare,
then this new method of reporting could be made an option.
      I am a new user of kompare,  it's cool,  and I do think it could be very
useful 
in assuring that there are no "accidental" updates to my website directories.   
If you want further clarification or discussion, please contact me at 
plainj at ieee.org       Thanks,  Jay

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.