[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: X-KDE-NativeMimeType weirdness
From:       Thomas <zander () xs4all ! nl>
Date:       2000-10-30 8:32:06
[Download RAW message or body]

> On Sunday 29 October 2000 17:35, Stephan Kulow wrote:
> > Waldo Bastian wrote:
> > > On Sunday 29 October 2000 15:57, Stephan Kulow wrote:
> > > > Waldo Bastian wrote:
> > > > > On Sunday 29 October 2000 14:41, you wrote:
> > > > > > Waldo Bastian wrote:
> > > > > > > On Sunday 29 October 2000 11:07, you wrote:
> > > > > > > > I compiled and installed koffice just today, on October 29th.
> > > > > > > > So, in order to fix the problem for good, should make install
> > > > > > > > in the koffice package set the dates to the current one,
> > > > > > > > instead of keeping October 16th around?
> > > > > > >
> > > > > > > That would probably help a lot.
> > > > > > >
> > > > > > > Stephan: Would that be possible?
> > > > > >
> > > > > > No, that wouldn't be possible. And I don't see how it would help.
> > > > > > RPMS don't set the date to current either
> > > > >
> > > > > Ok. Then we just have to rebuild unconditionally whenever we start
> > > > > KDE.
> > > > >
> > > > > Now that KConfig is up to speed that shouldn't be too bad.
> > > >
> > > > I don't really understand the problem. Files shouldn't get older,
> > > > everything
> > > > in KDE keeps the time stamp and RPM does too, so you should only get
> > > > updates
> > > > or new files. If a file didn't change it's time stamp it didn't change
> > > > it's
> > > > contents either. Do you check for increasing time stamps or at
> > > > changing?
> > >
> > > Increasing.
> >
> > That's wrong I would say. What do you expect to have happened when the
> > timestamp decreases?
> 
> Well, I don't store the modification time of each file. I only know the 
> creation date of the database and rebuild when a file with a more recent 
> modification date than the database is encountered.
> 
> It's clear now that that doesn't work very well.

if you look at the modified date of these .desktop files you will notice 
that these are set to the date the orig file was created (which is what
creates problems) if you however look at the Created Date of the file the
install data is set. If you look at that in the scan, I think that would 
solve your problem with filedates.

-- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new

[prev in list] [next in list] [prev in thread] [next in thread]