public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] download problem in ebuild
Date: Wed, 24 Aug 2005 23:49:29 +1200	[thread overview]
Message-ID: <1124884170.16165.15.camel@sf.rout.dyndns.org> (raw)
In-Reply-To: <20050824003827.GD28369@nightcrawler>

On Tue, 2005-08-23 at 19:38 -0500, Brian Harring wrote:
> On Wed, Aug 24, 2005 at 12:34:41PM +1200, Nick Rout wrote:
> > Thanks to all of you, thats now very clear.
> > 
> > The message i have is that it will work, but its not allowed.
> Wrong interpretation- it won't work within an ebuild.
> It requires exteneral user intervention to make the ebuild work, 
> *every* time.
> 
> Won't work == not allowed in this case, cause it... won't work for 
> ebuilds...

OK thanks again.

Actually the problem has been solved (sort of) because they also have a
sourcforge account, and I can see how the sourceforge mirror:/
specification works in URI_SRC. sweet.

Now to persuade the plonkers to remeber to post new versions to sf. I
dunno, people come to gentoo-user asking about how to get their stuff
into gentoo, and ya have to reorganise their whole darned project.

Never mind, I am learning in the process!

> 
> Etc.
> ~harring
-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2005-08-24 11:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23  2:33 [gentoo-dev] download problem in ebuild Nick Rout
2005-08-23  2:38 ` Georgi Georgiev
2005-08-23  5:02   ` Nick Rout
2005-08-23  2:39 ` Mike Frysinger
2005-08-23  2:41 ` Marius Mauch
2005-08-24  0:11   ` Nick Rout
2005-08-24  0:15     ` Brian Harring
2005-08-24  0:16     ` Mike Frysinger
2005-08-24  0:23     ` Chris Gianelloni
2005-08-24  0:34       ` Nick Rout
2005-08-24  0:38         ` Brian Harring
2005-08-24 11:49           ` Nick Rout [this message]

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=1124884170.16165.15.camel@sf.rout.dyndns.org \
    --to=nick@rout.co.nz \
    --cc=gentoo-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