Re: [gentoo-portage-dev] Downloading while compiling - FETCHCOMMAND inside.

[Roman Gaufman]

Well, that also works I suppose, I just don't like prozilla. In anycase with 
your solution if for the first URL you get file not found, or any other fetch 
error, you will need to remove lock file manually, you don't have that 
problem with my solution.

On Monday 29 March 2004 18:10, Wiebel wrote:
> My understanding of a lockfile seems to be different from your's so i'd
> come up with something like:
>
>
> FETCHPROG=proz
> FETCHCOMMAND="(
> while [ -e \${DISTDIR}/`basename \${URI}`.lock ]; do
> sleep 5; done &&
> if [ ! -e \${DISTDIR}/`basename \${URI}` ]; then
> touch \${DISTDIR}/`basename \${URI}`.lock;
> \$FETCHPROG \${URI};
> rm \${DISTDIR}/`basename \${URI}`.lock;
> fi
> )"
>
> in this case error handling remains on the FETCHPROG side.
>
>
>
> On Mon, 29 Mar 2004 14:39:05 +0000
>
> Roman Gaufman <hackeron@×××××××××.com> wrote:
> > This fetchcommand will make sure portage doesn't download file
> > simulatneously if you emerge -f package and emerge package in another
> > terminal, it will make it wait for package to finish download.
> >
> > I improved it a little. Now if download fails (e.g. file not found), it
> > wont freeze portage and will carry on, enjoy:
> >
> > FETCHCOMMAND="(
> > while [ -e \${DISTDIR}/`basename \${URI}`.lock ]; do
> > sleep 5; done &&
> > if [ ! -e \${DISTDIR}/`basename \${URI}` ]; then
> > /usr/bin/wget -t 5 --passive-ftp \${URI} -O \${DISTDIR}/`basename
> > \${URI}`.lock &&
> > mv \${DISTDIR}/`basename \${URI}`.lock \${DISTDIR}/`basename \${URI}` ||
> > rm \${DISTDIR}/`basename \${URI}`.lock; fi
> > )"
> >
> > Please help test. And suggest a solution to remove lock file if user
> > ctrl+c out of the wget.
>
> --
> gentoo-portage-dev@g.o mailing list

--
gentoo-portage-dev@g.o mailing list