On Mon, 10 Jan 2005 09:08:21 -0800, darren kirby
<[EMAIL PROTECTED]> wrote:
> "emerge --fetchonly system" will decide which packages you need and only
> download them to distfiles directory. If portage is telling you it wants to
> download a package that you have manually put in distfiles, it is probably
> because of a discrepancy in versions between 2004.2 and 2004.3.
> 
> Use the verbose flag "-v" and portage will print the size of the download...if
> it reports 0kb for a package, then it will use the version already in
> distfiles and not download.
> 
> -d

I didn't reply to this for a while since I was trying out what was
suggested and waited until I had got all the files correctly and got
from stage2 to stage3.

I've managed that and in the mean time I have run into a few issues
that I had to overcome. First was trying to use nptl straight off,
seems to be some issue with emerging the 2.6 kernel, and after a
suggestion of just removing that use flag and uninstalling the 2.6
kernel headers until I got the system build I went ahead and used the
2.4 kernel to start off first.

now I've got around to adding the nptl use flag back in and I've going
to move the system to a 2.6 kernel but I've noticed the following
behaviour with emerge.

running;
"emerge --newuse -p system"

outputs the following:
Calculating system dependencies ...done!
[blocks B     ] sys-kernel/linux-headers (from pkg
sys-kernel/linux26-headers-2.6.8.1-r2)
[ebuild  N    ] sys-kernel/linux26-headers-2.6.8.1-r2
[ebuild   R   ] sys-libs/glibc-2.3.4.20041102


adding the -v option tells me that
"sys-kernel/linux26-headers-2.6.8.1-r2" is a 77kB download and the
rest are already present.

However running
"emerge --newuse -fp system"

generates url's for all the files require in each of those packages,
which if you need to retreive remotely isn't all that good for
generating a file with url's in it.

Since I haven't got to understand all of emerge's functionality I
still think that my original thought is therefore correct, that it
doesn't appear to have the functionality to output "ONLY" the url's of
the files required.

I wrote a small script that would call emerge -p with whatever you
entered on the commandline in front of the script.
"emerge -p $command_line"

Should you enter
dl-list --newuse system  (dl-list was the name of a script that did
some of what emerge does these day's)
it call's
emerge -p --newuse system 

and spots that there are 3 packages to be examined, it then locates
and reads (if it exists) the digest file for the particular package.
It checks the md5sum (not the size just yet) of the corresponding
files and only outputs the url's of the files that need to be
retreived (although it doesn't handle 3rd party mirrors at the
moment).


So far its been pretty accurate with the exception of not generating
the url's for packages on 3rd party mirror sites at the moment, but
asside from that it just covers the files that need to be retreived.
The latest case it has proven accurate again indicating that there is
actually only 1 file to be retreived.


Have I missed that functionality in emerge or is it something that has
yet to be added. The generate of url's for all packages may be fine in
most cases but I don't like having to have a server retreive addition
files that are unnecessary and then having to carry them home on a
pendrive only to find out that I didn't need most of the files.


It seems a little strange to me that you can use "emerge --fetchonly
package" which will generate a list of dependancies and check the size
and md5sum's of any of the source files for these found in the
distfiles folder and only retreive the required files, and you can use
"emerge --fetchonly -p package" and it will generate url lists of the
package and any dependancies that are not yet installed or need to be
rebuild, and yet you cannot combine the features of both to check the
files already downloaded and just output the url list of files that
need to be downloaded.


-- 
Darragh Bailey
"Nothing is foolproof to a sufficiently talented fool"

--
[email protected] mailing list

Reply via email to