public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wiebel2001@t-online.de (Wiebel)
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Downloading while compiling - FETCHCOMMAND inside.
Date: Tue, 30 Mar 2004 02:37:32 +0200	[thread overview]
Message-ID: <20040330023732.10286867.Michael.Waiblinger@web.de> (raw)
In-Reply-To: <200403291935.31558.hackeron@dsl.pipex.com>

ok my point wasn't prozilla this could easily changed to FETCHPROG=wget or whatever you prefer. Due to the fakt I'm not working with && after the fetching you also are not to remove the lockfile even if the $FETCHPROG returnes with a failure. But after all it's simply a question of your personal preferences. My main point was, that a lockfile is not to contain any data at all, for my taste it only should be a empty file as a token of aktivity.


On Mon, 29 Mar 2004 19:35:31 +0000
Roman Gaufman <hackeron@dsl.pipex.com> wrote:

> 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.
> >
> >
> >

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


  reply	other threads:[~2004-03-30  0:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07 13:18 [gentoo-portage-dev] emerge feature request: Downloads managed by lock file system Thomas Horsten
2004-02-07 17:04 ` Simon Mika
2004-02-07 17:17   ` Sven Vermeulen
2004-02-07 22:07     ` Jeff Smelser
2004-02-08  0:59       ` Thomas Horsten
2004-03-28  0:21         ` Roman Gaufman
2004-03-29 14:39           ` [gentoo-portage-dev] Downloading while compiling - FETCHCOMMAND inside Roman Gaufman
2004-03-29 18:10             ` Wiebel
2004-03-29 19:35               ` Roman Gaufman
2004-03-30  0:37                 ` Wiebel [this message]
2004-04-04 11:38                   ` Brian Harring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040330023732.10286867.Michael.Waiblinger@web.de \
    --to=wiebel2001@t-online.de \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox