Mailinglist Archive: zypp-devel (84 mails)
| < Previous | Next > |
[zypp-devel] .solv files
- From: Peter Poeml <poeml@xxxxxxx>
- Date: Mon, 18 Aug 2008 12:36:59 +0200
- Message-id: <20080818103659.GM32558@xxxxxxx>
Hi,
I noticed a new file type on mirrors, a repo.solv file.
http://ftp.nux.ipb.pt/pub/dists/opensuse/repositories/Apache:/Modules/Apache_openSUSE_10.3/repodata/repo.solv
It turned up in the build service, but I assume it could also turn up in
distro or update trees. I need to know how to handle these files and
would appreciate some details about them. I suppose they should be
treated like .xml files resp. .xml.gz files in the build service tree,
because they are probably regenerated each time the repo metadata is
recreated?
It is explained here
http://www.mirrorbrain.org/files/talks/download-infra.pdf (page 55)
why this is important to know.
Just a note: in general, it is very helpful to notify ftpadmin when new
kind of content is created, since the content needs to be distributed
appropriately. Things that you do at metadata level can have significant
effects on our infrastructure and how it serves our users :-)
Thanks,
Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development
I noticed a new file type on mirrors, a repo.solv file.
http://ftp.nux.ipb.pt/pub/dists/opensuse/repositories/Apache:/Modules/Apache_openSUSE_10.3/repodata/repo.solv
It turned up in the build service, but I assume it could also turn up in
distro or update trees. I need to know how to handle these files and
would appreciate some details about them. I suppose they should be
treated like .xml files resp. .xml.gz files in the build service tree,
because they are probably regenerated each time the repo metadata is
recreated?
It is explained here
http://www.mirrorbrain.org/files/talks/download-infra.pdf (page 55)
why this is important to know.
Just a note: in general, it is very helpful to notify ftpadmin when new
kind of content is created, since the content needs to be distributed
appropriately. Things that you do at metadata level can have significant
effects on our infrastructure and how it serves our users :-)
Thanks,
Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development
| < Previous | Next > |