From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Smalltalk/X
Date: Sun, 9 Jun 2002 17:32:00 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.96.1020609172818.29387D-100000@pluto.prosalg.no> (raw)
In-Reply-To: <3D02F840.9080603@seul.org>
On Sun, 9 Jun 2002, Marko Mikulicic wrote:
> I don't understand. Does this mean that those packages cannot be
> download from the original url but only from your mirror. This
> solves a problem, but raises other: if the package is not in the mirrors,
> or the mirror is down, or the package is not yet in CVS ?
As you can specify a sequence of mirrors in /etc/make.conf, it is less
likely that our mirrors will be down than that
djs.ddid.shf.in/~varajana/tmp/tmp/foo/foo/tmp.tgz will be :P
> This means that while I'm writing the package I cannot test it
> completly (at least not the download) until it is copied to the mirrors.
That is a correct, but should be considered a minor matter, as this step
will be performed by the developer committing your ebuild for you.
> What SRC_URI should I put in the .ebuild ? Only
> http:/nowhere/${PN}-${PV}.tar.gz ?
I guess that is okay. http://www.ibiblio.org/gentoo/${PN}-${PV}.tar.gz is
also okay, as this (most likely) is where the package will reside (before
it is spread to our mirrors.
In fact, I think just "${PN}-${PV}.tar.gz" should work, but I have not
tested that.
Karl T
prev parent reply other threads:[~2002-06-09 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 16:29 [gentoo-dev] Smalltalk/X Marko Mikulicic
2002-06-09 0:20 ` Karl Trygve Kalleberg
2002-06-09 6:40 ` Marko Mikulicic
2002-06-09 10:35 ` Defresne Sylvain
2002-06-09 15:32 ` Karl Trygve Kalleberg [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=Pine.LNX.3.96.1020609172818.29387D-100000@pluto.prosalg.no \
--to=karltk@prosalg.no \
--cc=gentoo-dev@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