<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#ffffff"> <style type="text/css">blockquote {color: navy !important; background-color: RGB(245,245,245) !important; padding: 0 15 10 15 !important; margin: 15 0 0 0; border-left: #1010ff 2px solid;} blockquote blockquote {color: maroon !important; background-color: RGB(235,235,235) !important; border-left-color:maroon !important} blockquote blockquote blockquote {color: green !important; background-color: RGB(225,225,225) !important; border-left-color:teal !important} blockquote blockquote blockquote blockquote {color: purple !important; background-color: RGB(215,215,215) !important; border-left-color: purple !important} blockquote blockquote blockquote blockquote blockquote {color: teal !important; background-color: RGB(205,205,205) !important; border-left-color: green !important}</style>Seth Vidal <a class="moz-txt-link-rfc2396E" href="mailto:skvidal@fedoraproject.org"><skvidal@fedoraproject.org></a> wrote on ‫جمعه ۲۸ اوت ۰۹، ۲۲:۰۳:۱۰‬: <blockquote style="border-left: 2px solid rgb(16, 16, 255); color: navy; background-color: rgb(245, 245, 245); padding-left: 15px;" cite="mid:alpine.LFD.2.00.0908281329340.28337@localhost.localdomain" type="cite"> On Fri, 28 Aug 2009, Hedayat Vatnakhah wrote: <blockquote type="cite"> You don't need to know about all existing repositories, since you can still resolve file level dependencies. In such cases you'll be forced to download the other file I mentioned (primary_file_deps.db). I don't see why you'll need to recreate all repos when one of them changes! Sorry :( And its impossible to state anything about the last item. </blockquote> You're going to pretty much instantly download the complete filelists then b/c if you add ANY 3rd party repo you're going to need /bin/sh probably immediately along with various and sundry items in /etc/. </blockquote> Yes, that's true if the third party repositories do not use this feature. BTW, I think if you make an exception for /bin/ and /etc/ contents, you'll still save a reasonable amount of space in the primary repo (I think it would be enough to remove library dependencies). <blockquote style="border-left: 2px solid rgb(16, 16, 255); color: navy; background-color: rgb(245, 245, 245); padding-left: 15px;" cite="mid:alpine.LFD.2.00.0908281329340.28337@localhost.localdomain" type="cite"> Now - an argument could be made for nuking /bin/sh deps from orbit but that's going to have to happen at another layer than this. <blockquote type="cite">IMHO, even a single php/python script can provide such a XML RPC service (web service was just an example). Mirrors could get this file just like the other files when syncing. But well, it'll be http only. The GPG sign issue could be problematic, but would you really need to sign the traffic?! </blockquote> 1. a lot of our mirrors won't want to run any app 2. some of our mirrors are not running on linux (or sometimes not even on a unix) 3. it makes 'mirroring' things much harder in the traditional sense 4. yes you need to sign it otherwise you'll get the same set of problems we just dealt with last fall. We have to sign the metadata to make sure clients aren't screwed. </blockquote> OK, so, the last item is enough to reject the whole idea. Thanks, Hedayat <blockquote style="border-left: 2px solid rgb(16, 16, 255); color: navy; background-color: rgb(245, 245, 245); padding-left: 15px;" cite="mid:alpine.LFD.2.00.0908281329340.28337@localhost.localdomain" type="cite"> -sv </blockquote> </body> </html>