Re: [gentoo-portage-dev] Hello

[ashish gawarikar <ashish@sendmail.com>]

>Hm, I am afraid there is no trivial way to do this, short of collating 
>contents of all these packages in a single ebuild. However this:
>1. is ugly
>2. will not work if there are interdependencies within this set of packages
>  
>
That is the exactly why I doing this. We plan to deploy the packages 
included that have right interdependencies.

>Well, it should be possible if you split this package in two (and if it is 
>only the downloading part that you want to combine): 
>one downloads and unpacks the meta-tarball that you package yourself (should 
>have src_unpack placing extracted individual tarballs into ${D}/${DISTDIR} 
>and empty scr_compile/install)
>second just lists the dependencies as mentioned before.
>
>  
>
so you mean something like
dummy-download-1.0.0.ebuild => contains foo/bar etc
dummy-extract-1.0.0.ebuild => something like kde-base?

>Although I fail to see why would you want to do something like that. I mean 
>what is the situation when it is better to roll your own meta tarballs rather 
>than fetch individual ones? Well, bittorrent will be more efficient with 
>single large package rather than multiple small ones, but other than that I 
>am quite puzzled :).
>
>  
>

The advantage of doing this is viz:

1. QA has to test one huge download and dont have to test different 
scenarios.
2. You exactly know what packages you are getting in this download
3. You have to issue one-and-only-one command for upgrade


Thanks for all your help,

Ashish

--
gentoo-portage-dev@gentoo.org mailing list