This is a multi-part message in MIME format. --------------050704090004070608090606 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit No no.. the header reading is done manually, not using (lib)rpm the whole concept is to do a 'ls' on a ftp site, fetch & save (only) the headers, and generate a local headers.info file. Then on client processing side of things, nothing changes for yum so there's no negative impact on functionality Requires a bit of low level hacking and understanding of rpm file internals, but it's not rocket science (see http://www.rpm.org/max-rpm/s1-rpm-file-format-rpm-file-format.html for info on the lead, signature and header part of rpm files) seth vidal wrote: >On Tue, 2003-06-24 at 08:24, Chris Chabot wrote: > > >>Thing is, i'm working on a few other posible patches for yum.. two of >>which would depend on non-compressed headers. >> >>One is a proof-of-concept tool that downloads the headers from a >>normal redhat ftp server (open rpm file, only read in & parse sig, >>lead and header part of the file, and save header to disk and generate >>a local header.info), and one to parse up2date saved headers. >> >>Both would rely on non compressed .hdr parsing ;-) >> >> > >The first is asking for trouble in keeping things updated. Keeping up >with a unindexed repository will be a serious pain in the ass. I looked >into it in some detail. > >Also reading _just_ the header from a remote site will require turning >off any signature checking in rpm as rpm 4.2 and above will want to read >the whole file in, otherwise. > >-sv > > >_______________________________________________ >Yum mailing list >Yum@xxxxxxxxxxxxxxxxxxxx >https://lists.dulug.duke.edu/mailman/listinfo/yum > > --------------050704090004070608090606 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> <font face="Verdana">No no.. the header reading is done manually, not using (lib)rpm<br> <br> the whole concept is to do a 'ls' on a ftp site, fetch & save (only) the headers, and generate a local headers.info file. Then on client processing side of things, nothing changes for yum so there's no negative impact on functionality<br> <br> Requires a bit of low level hacking and understanding of rpm file internals, but it's not rocket science (see <a class="moz-txt-link-freetext" href="http://www.rpm.org/max-rpm/s1-rpm-file-format-rpm-file-format.html";>http://www.rpm.org/max-rpm/s1-rpm-file-format-rpm-file-format.html</a> for info on the lead, signature and header part of rpm files)<br> <br> <br> </font><br> seth vidal wrote:<br> <blockquote type="cite" cite="mid1056458228.24470.16.camel@binkley"> <pre wrap="">On Tue, 2003-06-24 at 08:24, Chris Chabot wrote: </pre> <blockquote type="cite"> <pre wrap="">Thing is, i'm working on a few other posible patches for yum.. two of which would depend on non-compressed headers. One is a proof-of-concept tool that downloads the headers from a normal redhat ftp server (open rpm file, only read in & parse sig, lead and header part of the file, and save header to disk and generate a local header.info), and one to parse up2date saved headers. Both would rely on non compressed .hdr parsing ;-) </pre> </blockquote> <pre wrap=""><!----> The first is asking for trouble in keeping things updated. Keeping up with a unindexed repository will be a serious pain in the ass. I looked into it in some detail. Also reading _just_ the header from a remote site will require turning off any signature checking in rpm as rpm 4.2 and above will want to read the whole file in, otherwise. -sv _______________________________________________ Yum mailing list <a class="moz-txt-link-abbreviated" href="mailto:Yum@xxxxxxxxxxxxxxxxxxxx";>Yum@xxxxxxxxxxxxxxxxxxxx</a> <a class="moz-txt-link-freetext" href="https://lists.dulug.duke.edu/mailman/listinfo/yum";>https://lists.dulug.duke.edu/mailman/listinfo/yum</a> </pre> </blockquote> </body> </html> --------------050704090004070608090606--
