Mailinglist Archive: opensuse (5130 mails)

< Previous Next >
Re: [opensuse] [RFC] Reducing Online Update Requirements
  • From: Pascal Bleser <pascal.bleser@xxxxxxxxx>
  • Date: Sat, 20 May 2006 13:48:45 +0200
  • Message-id: <446F021D.5040007@xxxxxxxxx>
Hash: SHA1

Sven Burmeister wrote:
(big snip, just wanted to comment on one point)

>> 2) By Design. Date of last change in update source could probably
>> be displayed in the UI, but this still doesn't give you the
>> ability to find out whether there was a more recent change.
>> Suggestion: Get timestamp of last released update (and only
>> that timestamp) from central location, e.g. by HTTP download
>> of a signed timestamp.txt.
> I proposed this when 9.3 was recent, do not know what happened to it, since
> the bug-reports from back then are not open.

Note that this is not feasible because you can't just invent new files
in repositories. The yast2 repository format certainly is under control
and could be enhanced by such a file, but it's not that simple, there
are quite a few 3rd party repositories out there as well.
Also, YaST2 supports RPM-MD (aka yum) repositories since SUSE 10.0, and
that format is a "standard" (more or less) and people use createrepo to
generate RPM-MD metadata. createrepo doesn't know anything about a
timestamp.txt and would have to be modified to do that - only for SUSE.
That's not necessarily a good idea.

The other option would be to retrieve the last modified timestamp of a
file that's part of the already generated metadata (preferably one that
changes with every metadata generation run ;)).
For example:
- - for RPM-MD: <URL>/repodata/filelists.xml.gz
- - for yast2: <URL>/setup/descr/packages

But that depends on the respective network protocol. It can be done with
FTP. I don't know about HTTP, don't think it's possible.

- --
-o) Pascal Bleser
/\\ <pascal.bleser@xxxxxxxxx> <guru@xxxxxxxxxxx>
_\_v The more things change, the more they stay insane.
Version: GnuPG v1.4.2 (GNU/Linux)


< Previous Next >