On Sunday 06 March 2005 21:09, Patrick Lauer wrote:
(B> On Sun, 2005-03-06 at 12:50 +0100, Fredrik Klasson wrote:
(B> > -----BEGIN PGP SIGNED MESSAGE-----
(B> > Hash: SHA1
(B> >
(B> > Chris White wrote:
(B> > | 2) access to an internal download library built into portage (not wget
(B> > | or some such). This would not only allow us to do basic downloading,
(B> > | but also address new protocols that come later on.
(B> >
(B> > uhm, just a radnom thought struck me, why re-invent the wheel? What I'm
(B> > thinking is that, why not simply provide some Download Abstraction Layer
(B> > (DAL) or something like that, ie, "downloadThisFileForMe(filename);"
(B>
(B> I think that was the idea.
(B> You tell portage "use that download wrapper" in a config file, then just
(B> invoke "portage.fetch("URI")
(B
(BI think URI is even taking it too far. Even fetching of individual files
(Bdoesn't seem to be required. All that's really needed is to tell portage to
(Bfetch the required files for any particular package.
(B
(BIf you want to be able to download individual files for use outside of portage
(Bthen you'll need to know where they are going and whatever else. If you want
(Ball that, you can grab the URI from SRC_URI and do it manually.
(B
(BRegards,
(BJason Stubbs
(B--
([email protected] mailing list
